This is like a "water is wet" post for me. Maybe it is because I have been doing this so long... maybe for another reason. But people need to hear it. The impo

This is like a "water is wet" post for me. Maybe it is because I have been doing this so long... maybe for another reason. But people need to hear it. The important part is buried at the bottom and I'll re-summarize in less words: Start with high code quality standards [with proficient, experienced devs] delivering the minimal amount of functionality to ship. Then rinse and repeat. With experience comes a developed taste for the general work of software development and a better discernment for where to draw the lines. How to decouple and how to recognize when the decoupling is wrong and refactor. And how to refactor appropriately without making up fear based excuses. If you are interested in more checkout "A Philosophy of Software Design" by Ousterhout, "Righting Software" by Löwy and "Mythical Man Month" by Brooks.