The dude is right and I strongly side with him however, what is missing is that I oscillate like the TV megahertz that powered the first commercial Pang games between states and this open the space for more grey in between altered states like “Ok, will fix later. Let’s put a #TODO and ship it.”
So instead of criticizing the gentleman for its dichotomy I feel like adding more states to it to complete the picture. And I mean it, this is not making fun of someone it means I tamed myself in stopping to do premature optimization knowing Gigahertz won’t care about me saving a cycle and might even hinder the masterfully crafted compilers from optimizing even more.
3. Partly awesome, partly not so much but don’t need to be awesome.
4. Myself has to understand this masterpiece of human thinking in six months and more from here and after a 20 hour stint I myself marvel at the result so better comment before committing the code into oblivion.
5. Embarrassing, but people are delighted.
6. This made headlines years ago, but some code doesn’t age well.
7. OMG, OOP might looks right, but a new paradigm rushes me into refactoring frenzy and makes the code look better without breaking any features!
8. I used tool to check for bottlenecks and it runs well, but looks crap. So what do I do?
9. Loop unrolling is still a thing or not? Do compilers have headaches just like I do? Do they really care or simply follow orders or adjust to the target platform and settings?
So instead of criticizing the gentleman for its dichotomy I feel like adding more states to it to complete the picture. And I mean it, this is not making fun of someone it means I tamed myself in stopping to do premature optimization knowing Gigahertz won’t care about me saving a cycle and might even hinder the masterfully crafted compilers from optimizing even more.
3. Partly awesome, partly not so much but don’t need to be awesome.
4. Myself has to understand this masterpiece of human thinking in six months and more from here and after a 20 hour stint I myself marvel at the result so better comment before committing the code into oblivion.
5. Embarrassing, but people are delighted.
6. This made headlines years ago, but some code doesn’t age well.
7. OMG, OOP might looks right, but a new paradigm rushes me into refactoring frenzy and makes the code look better without breaking any features!
8. I used tool to check for bottlenecks and it runs well, but looks crap. So what do I do?
9. Loop unrolling is still a thing or not? Do compilers have headaches just like I do? Do they really care or simply follow orders or adjust to the target platform and settings?