Re:The 'premature optimization is evil' myth (2010)
by ubernostrum on Monday March 14, 2016 @04:15PM
(#11285250)
I prefer the development order of make it work, make it correct, then make it fast. Expresses a similar idea, but in terms of priorities instead of "don't do that at all".
Re:The 'premature optimization is evil' myth (2010)
by vmorgulis on Monday March 14, 2016 @05:51PM
(#11285832)
> Expresses a similar idea, but in terms of priorities instead of "don't do that at all".
The programming language affects a lot the criterion. Some are known to be "correct" (like Haskell), others "fast" (like C) ...
Given an infinite amount of time, I suppose the three can be reached in any language.
It's not that all issues are preventable. It's that you can prevent a lot of them with just a little extra work up front.
It's a misuse of Knuth's original point, which has much more to do with how brittle and incomprehensible "optimized" code can become.