Those definitely make them less wrong, but still leave you hanging because most functions have side effects and those are exceedingly difficult to trace. The f

Those definitely make them less wrong, but still leave you hanging because most functions have side effects and those are exceedingly difficult to trace. The function that triggers GC is typically not the function that made the mess. The function that stalls on L2 cache misses often did not cause the miss. Just using the profiler can easily leave 2-3x performance on the table, and in some cases 4x. And in a world where autoscaling exists and computers run in batteries that’s a substantial delta. And the fact is that with few exceptions nobody after 2008 really knows me as the optimization guy, because I don’t glorify it. I’m the super clean code guy. If you want fast gibberish, one of those guys can come after me for another 2x if you or I don’t shoo them away. Now you’re creeping into order of magnitude territory. And all after the profiler stopped feeding you easy answers.