3 ms·
> Premature optimisation is a problem, but I'd say in general it's a better approach to just start out by doing the fast thing This is contradictory
by davedx 7y ago
> Premature optimisation is a problem, but I'd say in general it's a better approach to just start out by doing the fast thing
This is contradictory
- ragnese 7y agoThe keyword is "premature". The whole silly meme of "premature optimization is the root of all evil" is a 100% useless statement. Of course, you shouldn't do it yet if it's premature- that's the definition of premature. But if it's almost the same amount of effort to write faster code from the get go- especially if you KNOW the code will be speed-sensitive, then you should absolutely try to do the fast thing over the slow thing. That seems obvious...