A sustainable application remains reliable, flexible, and maintainable throughout a long lifespan of deployment, use, bug fixes, feature additions, and changing requirements. section 1.0 section 1.3
Good design makes sustainability practical by ensuring that software:
- Meets requirements and behaves as users expect. section 1.3
- Passes tests, has fewer bugs, and avoids hidden runtime performance problems. section 1.3
- Adapts systematically as features and requirements change. section 1.3
From patch tangle to sustainable release
A quick hack may suit a one-time task, but repeated patches for bugs and features can become an unmanageable tangle. Better design supports testing, reaches minimum viable product sooner, and accommodates later changes. section 1.3
Sustainability emerges through requirements analysis, design principles, design patterns, testing, and repeated development iterations; backtracking may be necessary to recover from poor decisions. section 1.0

