The realization that good architecture and coding practices are critical has led to a rise in the notion of 'high-optionality software development' — that development teams should work to keep change options open.
A hero developer built a crucial feature in an inscrutable manner, making it difficult for her colleagues to understand the implementation once she left, showcasing the risks of individual-driven design.
The past belief that anyone with domain knowledge could become a developer has shifted, highlighting the pitfalls of rapid application development and the temptation to ship prototypes without proper foundations.
The inclination to ship prototypes without rewriting them leads to reliance on a fragile foundation, which impacts long-term maintenance and evolution of software.
Collection
[
|
...
]