4 ms·
> Namely you should write code that is fast and efficient I don't think this is accurate. I watched a talk with Jonathan Blow recently and he went on for quite
by arduinomancer 5y ago
> Namely you should write code that is fast and efficient
I don't think this is accurate. I watched a talk with Jonathan Blow recently and he went on for quite a while railing against premature optimization.
https://youtu.be/JjDsP5n2kSM?t=561 https://youtu.be/JjDsP5n2kSM?t=561
- jecel 5y agoPremature optimization makes it harder to write fast and efficient code. That is because you guessed where the bottlenecks would be before you had enough information (which is why it was "premature"). The optimizations make the code more brittle and hard to change so that when you reach a position to measure where the bottlenecks are it is too complicated to do the proper optimizations.