The Meaning of Connascent

From Latin Philosophy to Modern Software

A Proto-Indo-European root for birth, taken through Latin, dropped into English in 1805, and pulled back into use in 1992 by a programmer who needed exactly what it meant.

Connascent is a rare English adjective for “born together”, from the Latin present participle connāscēns. It first appears in English in 1805, in Thomas Taylor's philosophical writings, and then sits almost entirely unused until software engineers revive it in the 1990s as the name for a taxonomy of coupling between code components.

The word is rare. In ordinary English nobody reaches for it. The route it took to get here is the part worth tracing: a Proto-Indo-European root for birth, into Latin, into English in 1805 through Thomas Taylor, out of active use for almost two centuries, and back into service in 1992 when a programmer named Meilir Page-Jones needed exactly the word it already meant.

The sections below follow that path through etymology, the historical attestations, the botanical sense, and the current software-engineering sense.

Historical Timeline

The evolution of “connascent” from its first English usage to modern technical application

1646Natural philosophy

Connascency

Thomas BrownePseudodoxia Epidemica

First substantive English usage of the connāscent- stem in natural philosophical discourse.

1755Scholarly writing

Connascence

UnknownFirst recorded use

The noun form "connascence" appears in English, predating the adjective.

1805Philosophy

Connascent

Thomas TaylorMiscellanies, in Prose and Verse

Earliest documented use of "connascent" as an adjective in English, employed for Neoplatonic metaphysics.

1992Computer science

Software Engineering

Meilir Page-JonesCommunications of the ACM

Deliberate resurrection of the archaic term to describe code component coupling.

2009-2012Software architecture

Modern Popularity

Jim WeirichConference Talks

Repopularization through influential talks on software design and architecture.

Etymology and Proto-Indo-European Origins

Morphological Structure

con- (together) + -nasc- (be born) + -ent (present participial suffix)

The structure is plainly Latin and never got blurred. Because English borrowed the word from text rather than picking it up from speech, the spelling arrived intact and stayed that way; no significant variants are recorded.

Connascent comes from the Latin compound verb connāscī (“to be born together”). That verb is in turn built from the prefix con- (an assimilated form of cum, “with”) attached to nasci, a deponent verb meaning “to be born.”

Nasci is the Latin reflex of Proto-Italic *gnāskōr, which had already dropped the initial g- from the older Proto-Indo-European root *ǵenh₁- (“to give birth, beget, produce”).

Proto-Indo-European Root

*ǵenh₁- (“to give birth, beget, produce”)

The same root left descendants in most branches of Indo-European:

Greek: γεννάω (gennáō, “to beget”)
Sanskrit: janati (“begets, bears”)
Gothic: kuni (“race”)
Old English: cennan (“beget, create”)
Old High German: kind (“child”)
Latin: nātūra (“nature”)

In classical Latin, nascor (present infinitive nascī, perfect natus sum) was a deponent verb of the third conjugation, meaning it took passive endings but had an active sense. An older spelling gnascor kept the original consonant cluster, and the past participle gnātus stayed alive as a poetic variant of natus (“born”) in later Latin literature.

The present participle nāscēns gave English “nascent” (first recorded in the 1620s), and nātūra (literally “that which is born”) became “nature.” The compound connāscī specifically meant simultaneous birth or growth, with the con- prefix carrying the “with each other” sense.

Historical and Literary Usage

The word and its noun forms turn up in only a handful of historical texts. The four below are the more substantial uses, spanning philosophy, theology, and comparative religion.

1805
I believe, therefore, that such things as are produced by the first good in consequence of being connascent with it, do not recede from essential goodness, since they are immovable and unchanged, and are eternally established in the same blessedness.

Thomas TaylorMiscellanies, in Prose and Verse

Taylor's Neoplatonic use of the word. He is not describing things merely born at the same moment, but things bound to the divine principle by sharing eternally in its existence.

1801
But things are said to be rising into being, which receive increase through another thing by contact, or being connascent with it; as embryos...

Thomas TaylorThe Metaphysics of Aristotle (Translation)

Taylor uses the word to translate Aristotle on how some things come into being by touching or being born together with something else.

1817
No: had not Esther been involved in the edict against the Jews, by her connascence and her religious profession, Mordecai might have pleaded in vain for her perilous interference.

Mary GraftonSpiritual Gleanings

Here the word means shared heritage. The reference is to being born into the Jewish people, in a discussion of the book of Esther.

1933
It should be observed that the connascence (sahajanma) [Sanskrit सहजन्मा] of Father-essence and Mother-essence, the 'two forms' of Brahman, though metaphorically spoken of as 'birth' (janma), is not a sexual-begetting...

Ananda K. CoomaraswamyA New Approach to the Vedas

Coomaraswamy uses the English word to translate the Sanskrit sahajanma ("born together"). Father-essence and Mother-essence are described as arising together as a pair, rather than one giving rise to the other.

The OED Record

The OED gives 1805 as the earliest documented use of “connascent” as an adjective in English, and that single citation is the only one the dictionary carries for the adjective form. Taylor either coined the word himself for the Neoplatonic argument he was making, or pulled it from a Latin source no one else was reading at the time. Either way it never took. Connate (1641) and connatural (1599) were already in use and covered the same ground; connascent had nothing new to add.

Modern Technical Applications: Software Engineering

The main contemporary use of connascence is in software engineering and architecture, where it names a metric for the coupling between software components.

Computer scientist Meilir Page-Jones introduced the concept in his 1992 article “Comparing Techniques by Means of Encapsulation and Connascence” (Communications of the ACM, Volume 35, Issue 9), and expanded it in his 1996 book What Every Programmer Should Know About Object-Oriented Design. Programmer Jim Weirich picked the term back up between 2009 and 2012 in two conference talks: “Grand Unified Theory of Software Design” and “Connascence Examined.”

Technical Definition

“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.”

Another way of saying that some code elements share a destiny: they were born together in the design, and they cannot now be changed independently.

Page-Jones picked the word on purpose. In his own words: “I chose the word 'connascence' from the Latin roots meaning 'born together.' It is etymologically close to the French 'connaissance' meaning knowledge, awareness or consciousness.” Reviving a dead word for a technical concept is uncommon. Reviving one whose literal meaning is already exactly what you want is rarer still.

Three Dimensions of Connascence

1. Strength

How difficult the dependency is to discover or refactor

2. Locality

How physically or logically close dependent components are in the codebase

3. Degree

How many components are affected by the dependency

Static Connascence(Detectable at compile-time)

Connascence of Name (CoN)

Weakest

Components must agree on entity names

Example: Variable names, function names

Connascence of Type (CoT)

Weak

Components must agree on type signatures

Example: Data types, interfaces

Connascence of Meaning (CoM)

Moderate

Components must agree on interpretation of specific values

Example: Magic numbers, boolean flags

Connascence of Position (CoP)

Moderate

Components must agree on value ordering

Example: Parameter sequences, array indices

Connascence of Algorithm (CoA)

Strong

Components must agree on specific algorithms

Example: Encryption schemes, hash algorithms

Dynamic Connascence(Manifest only at runtime)

Connascence of Execution (CoE)

Strong

Execution order is critical

Example: Initialization sequences

Connascence of Timing (CoT)

Very Strong

Timing is crucial

Example: Race conditions, timeouts

Connascence of Values (CoV)

Strong

Multiple values must change together to maintain invariants

Example: Synchronized state

Connascence of Identity (CoI)

Strongest

Components must reference the same instance

Example: Singleton patterns, object references

Design Principles

  • Minimize overall connascence between components
  • Convert stronger forms to weaker forms where possible
  • Use weaker forms as distance increases between elements

The software engineering community has actively developed the concept with dedicated educational resources (connascence.io), integration into design methodologies, and application to emerging architectural patterns. The term has achieved standardization in professional discourse about code quality, appearing in architecture textbooks such as Mark Richards and Neal Ford's Fundamentals of Software Architecture (2020).

Botanical and Biological Usage

In botanical morphology, the related term “connation” (first recorded 1846) describes the developmental fusion of plant organs of the same type — petals fused to other petals, sepals to other sepals. The fused structures are called “connate.” It is the Latin root taken literally: the parts grow up together and end up joined.

Connation contrasts with “adnation,” which is fusion of different kinds of organs (a stamen fused to a petal, say).

Botanical Terminology

Specific terminology derived from the concept of connation:

Synsepalous: All sepals fused into a calyx tube with calyx lobes
Sympetalous: All petals fused into a tubular corolla (e.g., morning glory, Ipomoea)
Synandrous: Stamens fused in unspecified manner
Synfilamentous: Stamens fused by filaments
Synantherous: Stamens fused by anthers (common in Solanum species)
Syncarpous: Carpels fused to form compound ovary
Connivent: Like organs placed adjacent but not actually connected

Connate structures are diagnostic in plant taxonomy. Which floral parts are fused, and how completely, helps botanists tell families and genera apart, and feeds into work on evolutionary relationships between them.

Outside botany, classical biology used connascent for organisms developing at the same time, or structures arising together in an embryo. The word never took hold in modern biology as a standard term. Today the same concepts get more specific names: “conjoined twins” for twins physically connected at birth, and “concurrent,” “synchronous,” or “co-developing” for things happening at the same time.

The anatomical term “connate” survived in medical contexts to describe parts firmly united or fused, and in geology for “connate water” (water trapped in sediment at the time it was deposited, literally water “born together” with the sediment).

Semantic Evolution and Cross-Linguistic Perspectives

The core meaning (entities bound by shared origin) does not move much across these fields. What changes is which part of that meaning gets emphasized. Below are the four registers the word has worked in.

Classical Latin & Historical English (18th-19th centuries)

Strictly about timing. Two things born or originated at the same moment, with the shared moment understood to bind them in some way.

Philosophical Usage (Neoplatonic & Vedantic)

Extended beyond time into metaphysics. Things that arise together from a single source stay tied to that source, and to each other, permanently.

Botanical & Biological Usage

Physical rather than metaphysical. Plant organs or biological structures that grow together, often fusing into a single composite shape.

Software Engineering Resurrection (1992-present)

Structural rather than temporal. Two pieces of code are connascent if changing one forces a change in the other to keep the system correct. The “born together” image still fits: they came into being together in the design, and they cannot now be separated without consequences.

Cross-Linguistic Comparison

Latin nasci spawned ordinary vocabulary in every Romance language: French naître/naissance, Italian nascere/nascita, Spanish nacer/nacimiento, Portuguese nascer/nascimento. The compound form with con- did not travel with any of them. Romance speakers got the simple participial forms (naissant, nascente) for everyday use and left the prefixed version to specialists, when they bothered with it at all.

Page-Jones himself noted how close connascence sounds to French connaissance (“knowledge”), and that probably influenced his choice of the English word. The two are not actually related. Connaissance comes from Latin cognoscere (“to know”), not connascere (“to be born together”). They are different verbs that happen to land in roughly the same phonetic neighbourhood after centuries of French sound change. The pun is accidental, but it does some of the work of making the term feel familiar to a reader meeting it for the first time.

Contemporary Status

In general English the two words are dead. Dictionaries still list them and mark them obsolete. A modern writer who wanted to say “born together” or “happening at the same time” would reach for contemporary, coeval, simultaneous, concurrent, or synchronous instead, depending on which shade they wanted. The traditional senses survive only in academic translations of classical texts and in historical scholarship that quotes them.

General English

Status: Obsolete/highly archaic

Usage: Academic translations, historical scholarship

Alternatives: Contemporary, coeval, simultaneous, concurrent

Software Engineering

Status: Active, growing adoption

Usage: Professional discourse, code reviews, architecture

Resources: connascence.io, textbooks, conference talks

Botanical Sciences

Status: Stable in technical usage

Usage: “Connate” (not “connascent”) is standard term

Context: Systematic botany, plant morphology

Philosophy & Classics

Status: Historical curiosity

Usage: Classical text translations

Context: Neoplatonic, Aristotelian philosophy

Inside software engineering the picture is the opposite. Connascence has its own reference site (connascence.io), regular appearances in conference talks and architecture textbooks, and a working place in code reviews and architecture decision records. It now sits alongside the SOLID principles and Clean Architecture in the standard vocabulary developers use when they talk about coupling.

Other Words With a Split Life

The split between general obsolescence and active technical life is not unique to connascence. A few other words have had the same trajectory:

  • “Bit” — archaic English “fragment,” repurposed for binary digit
  • “Daemon” — mythological spirit, repurposed for background process

Conclusion: Two Centuries Between Lives

The path from PIE *ǵenh₁- to Page-Jones is long, but most of it is dead air. Latin had connāscī. English took the participial form in 1805 and almost never used it. Thomas Taylor wanted a word for the Neoplatonic idea of essences co-arising with the divine principle, and either coined it from Latin sources himself or pulled it from a text nobody had read in a while.

The reason it never caught on is ordinary. Connate (1641) and connatural (1599) already covered the same territory, and they had a head start of nearly two centuries. The Victorian period saw it surface a few more times in philosophical translation, religious writing, and the occasional scientific paper, and then it was gone. By 1900 the OED was carrying it as a single 1805 attestation with no live use behind it.

Page-Jones picks it up

In 1992 Meilir Page-Jones needed a name for the property that two pieces of code share when changing one forces a change in the other. He went looking in Latin for “born together” and found connascence sitting there, ninety years unused, with the meaning he wanted already attached.

That is most of the story. A word that almost died, picked up by a programmer because it precisely named a thing that needed a name. Today it is two words at once: an obsolete one in general English, and a working one inside software architecture.

Sources

Primary Historical Dictionaries and Reference Works

Etymology and Linguistic Sources

Historical Usage and Primary Sources

Software Engineering and Technical Sources

Botanical and Biological Usage

All sources accessed and verified during November 2024. This comprehensive article synthesizes information from 50+ academic sources across linguistics, philosophy, software engineering, and botanical sciences.