3 ms·
Your definition is off by the way, writing fast code and doing optimisation doesn't necessarily mean that the code will be less understandable or become brittle
by jlebar 11y ago
Your definition is off by the way, writing fast code and doing optimisation doesn't necessarily mean that the code will be less understandable or become brittle.
OP said
Optimization often involves making code less clear, more brittle
Seems you're arguing against a straw man here.
- blub 11y agoNot quite. * OP is arguing that optimisation is usually problematic from multiple perspectives. Here's the full quote: Optimization often involves making code less clear, more brittle, or with a more pasta-like organization. Frequently optimization requires writing code that if looked at out of context, doesn't make sense or might even look wrong. * I am arguing that these assumptions cannot be made so easily. Yes, they qualified the statements with "often" and "frequently", but the tone is clearly negative. It shouldn't be, and we shouldn't shun writing fast code out of the belief that it's at odds with readability or robustness.