> That is, performance bottlenecks are easier to find and fix if your code is clean to begin with That is not at all what "make it work, make it pretty, make i

> That is, performance bottlenecks are easier to find and fix if your code is clean to begin with That is not at all what "make it work, make it pretty, make it fast" is about. That saying is about prioritization. Making it fast doesn't mean anything if it doesn't work. However, if you are doing performance-sensitive work then this is a very bad strategy. You need to design a performant architecture up front otherwise you'll likely have orders of magnitude worse performance, even after optimizing your code. Ex: if your "make it work" design has shared mutable state, you're going to have a bad time when you want to scale that horizontally and unlock 100x better throughput/performance.