>The grandparent post isn't talking about over-optimizing. Nonetheless, warning bells go off inside my head whenever I hear that opinion expressed without the

>The grandparent post isn't talking about over-optimizing. Nonetheless, warning bells go off inside my head whenever I hear that opinion expressed without the caveat "if it isn't a problem for the user, leave it the fuck alone". >You shouldn't have to add disgusting hacks to complete a trivial operation in less than a second. If a trivial operation takes more than a second that's almost always indicative of a bigger underlying problem of crappy code. Cleaning up dirty code that incidentally causes performance improvements is fine, but changing code specifically to make performance improvements without improving its overall quality leads to a downward spiral of shit.