Stability and security over responding to change
In a world where technology changes constantly, it is almost impossible to stay tuned to all the novelties. Programming languages come and go, new frameworks emerge, all with miraculous promises. One thing is acting when necessary. Another is following the herd just because it became a fad.
The rewrite epidemic
The software industry suffers from a rewrite epidemic. With every new trendy language or framework, entire systems are rewritten from scratch, generating new bugs, new incompatibilities, and new missed deadlines — all in the name of “modernization”. The result is almost always a system worse than the one discarded.
Fad ≠ innovation
Changing for the sake of changing is waste. A stable, tested, and known system is worth more than the latest hype novelty. Stability allows the team to master the problem domain, and focus avoids the dispersion that undermines quality. Those who switch technology every quarter never mature anything — and maturing is what separates software from toys.
The house analogy
In an analogy, a solid house built with known and well-laid materials is preferable to a mansion of eco-bricks that collapses in the first storm for lack of limestone. The foundation takes time to cure — and that time is non-negotiable.
That is, as a rule, the more stable and focused a system is, the fewer unnecessary changes it undergoes.