“Clean” code, horrible performance
I think the author is taking general advice and applying it to a niche situation.<p>&gt; So by violating the first rule of clean code — which is one of its central tenants — we are able to drop from 35 cycles per shape to 24 cycles per shape<p>Look, most modern software is spending 99.9% of the time waiting for user input, and 0.1% of the time actually calculating something. If you&#x27;re writing a AAA video game, or high performance calculation software then sure, go crazy, get those improvements.<p>But most of us aren&#x27;t doing that. Most developers are doing work where the biggest problem is adding the next umpteenth features that Product has planned (but hasn&#x27;t told us about yet). Clean code optimizes for improving time-to-market for those features, and not for the CPU doing less work.