I think a lot of people forget the last part of, ship the first thing that works: it has to "work" for some reasonable expectations of fitness for purpose. Our

I think a lot of people forget the last part of, ship the first thing that works: it has to "work" for some reasonable expectations of fitness for purpose. Our short iteration times in software are the envy of many engineering professions but it's the fitness for purpose part that nips some of us. I don't necessarily believe Clean Code is the silver bullet to avoiding difficult to maintain code but some kind of standard is important. There are principles and patterns of design that are known to be effective which can be useful in guiding a project through the tactical phases from cascading poor short-term choices that lead to long-term technical debt. The economics seem like they should include many more factors. There's a time and a place where the effort for a correct-by-construction approach costs too much and the risk tolerance of introducing errors or incorrect behaviors is tolerable to the people funding the project. In such cases it's time to market we care about and nobody is going to lose much sleep if you lose 0.0005% of your SLOs over a 3 month window.