liveBook · Manning

Organic growth

As explained in The Coder Cafe

Organic growth is the gradual evolution of a software system through accumulated changes rather than centrally planned restructuring.

Organic growth is the gradual evolution of a software system through accumulated changes rather than centrally planned restructuring. In a codebase, incremental delivery and agile methodology shape the system from the bottom up as developers add solutions over time. section 4.12

This evolution reflects many developers’ differing mental models, biases, and ideas about the future. As people join and leave, the codebase records hundreds or thousands of local decisions, often producing a system without a consistent overall direction. section 4.12

Organic growth creates recognizable tradeoffs:

  • Preserves gradual delivery by allowing the system to respond to changing needs through incremental changes. section 4.12
  • Accumulates ad hoc solutions that can leave the codebase inconsistent and difficult to guide. section 4.12
  • Contrasts with controlled growth, where teams constrain what changes, decide where changes belong, and periodically review or rearrange the system. section 4.12

The public garden

Imagine a public garden where anyone can plant anything anywhere. It may become colorful, but it lacks harmony and guidance. A controlled garden limits what can be planted, places growth deliberately, and periodically reviews the arrangement. The contrast illustrates why organic growth can carry a negative connotation in software: accumulation alone does not provide direction. section 4.12

How The Coder Cafe covers it

How deep it goes
Defines the term, traces its causes, contrasts controlled growth, and illustrates consequences through a garden metaphor.
Examples
Uses evolving codebases, developer turnover, and an uncontrolled public garden contrasted with a periodically reviewed garden.
What it assumes
Assumes familiarity with codebases, developers, and agile methodology while defining organic growth explicitly.
What you can do after
Evaluate whether a codebase’s accumulated changes provide useful adaptation or reveal missing direction and coordination.
How it connects
Connects organic growth with agile methodology, incremental delivery, codebase evolution, and controlled growth.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of The Coder Cafe. The section links point to the parts of the book it draws on.