ActiveDraftPrinciple
03
Optimize for Maintainability
Write code for the engineer who maintains it next.
StatusActive
MaturityDraft
Versionv0.1.0
Created2026-07-01
Updated2026-07-01
References1
#maintainability#readability#longevity
Overview
Most of a system's cost is paid after it ships. We favour clarity, documentation and low coupling so the system stays cheap to change.
Why
The reasoning behind "Optimize for Maintainability" will be captured here — grounded in real engineering trade-offs rather than theory.
Standard
The concrete, enforceable expectations for "Optimize for Maintainability" will be defined here as the principle matures into a standard the team can hold each other to.
Examples
- A real example will be added once this principle has guided a shipped decision.
Counter Examples
- A real counter-example will be added from a decision that ignored this principle and paid for it.
Lessons Learned
- Lessons will accumulate here through applied engineering experience.
Related Principles· 1
Related Documents· 2
Referenced By· 1
Version History
- v0.1.0
Principle established with placeholder content.