9 ms·
I've never interpreted "Premature optimization..." to mean don't think about performance, just that you don't have to actually implement mechanisms to increase
by arethuza 1y ago
I've never interpreted "Premature optimization..." to mean don't think about performance, just that you don't have to actually implement mechanisms to increase performance until you actually have requirements to do so - you should always ask of a design "how could I make this perform better if I had to".
- aleph_minus_one 1y agoTo me, it rather meant: "Ultrahard" optimization is perfectly fine and a good idea, but not before it has become clear that the requirements won't change anymore (because highly optimized code is very often much harder to change to include additional requirements). Any different interpretation in my opinion leads to slow, overbloated software.
- arethuza 1y agoYeah - I've heard that described as "It's easier to make working things fast than fast thing work" - or something like that.