The most challenging principle of Agile is “simplicity — the art of maximizing the amount of work not done.” Developers waste immense cycles trying to avoid software failure. Rather than defining “good enough” reliability and stopping there, teams go way beyond the point of diminishing returns, building what is jokingly referred to as “gold plated” reliability infrastructure around their software. Fear of failure has instilled an all-or-nothing mindset to software reliability that is the opposite of Agile simplicity. The reason developers overbuild for reliability — and there are many ways you can over-engineer for performance, uptime, high availability, even security — is that they never really had a way to define “good enough” reliability in the first place. Without a clear picture of success or a clear finish line, developers can readily communicate with the organization. The big boss wants 100% reliability, and that leads to eye rolls from engineers. Eureka! SLOs Forever Changed
This website is about programming knowledge. You can call this blog best programming master.