” We should forget about small efficiencies, say about 97% of the time: premature optimization is the root of all evil.” As I've gotten older, I've developed t

” We should forget about small efficiencies, say about 97% of the time: premature optimization is the root of all evil.” As I've gotten older, I've developed the following interpretation of this statement: Getting system architecture right is hard, but crucial. When it is right, there is very little code to it, as little as necessary for the job. Rather than sprinting ahead and micro-optimizing your initial architecture, you should go slow, focus on minimal-viable units within the system and then, once contact with the real world has occurred, step back and ask if your architecture is going with the problem, akido style, or fighting it, J2EE style. Then, and only then, consider the perf fixes appropriate to whichever situation you find yourself in.