Two software components are connascent if a change in one would require the other to be modified in order to maintain the overall correctness of the system. Connascence is a way to characterize and reason about certain types of complexity in software systems.

The article is about Connascence applied to Ruby.

Link: Practicing Ruby – Issue #24: Connascence as a Software Design Metric