Most software is a bus terminus
The article argues that most software projects function like a bus terminus—they are built to a final, static state rather than as ongoing services, leading to decay once initial development ends. It contrasts this with software designed for continuous evolution and maintenance, suggesting that sustainable software requires treating it as a living system, not a finished product.
Background
- The article argues that most software projects end up as "bus termini": final stops where code gets frozen, abandoned, or becomes too costly to change, rather than evolving continuously.
- It contrasts this with "bus routes" — software that keeps moving, adapting, and being maintained over time.
- Key concept: software entropy — as code accumulates patches, workarounds, and outdated dependencies, it becomes harder and riskier to modify, eventually locking teams into maintenance mode or rewrites.
- The metaphor draws from Fred Brooks' "The Mythical Man-Month" (1975) and ongoing debates about technical debt, software lifecycle, and why most SaaS or internal tools stagnate after initial development.
- Implicit reference: the "rewrite trap" — teams often abandon a terminused codebase to build anew, only to repeat the cycle.