You would think this would encourage better optimized software, but I doubt devs will actually do that. Most modern code practices are about ensuring that code is more easily maintained, often at the cost of performance. Breaking “clean code” rules can easily make programs run 10-25x faster, but will be much harder to maintain.
We also seeing a lot of vibe coding now, which mixes clean code practices (which are well documents online) with messier, less well planned code.
That’s grossly over simplifying the problem. “Clean code” is also not a formally defined concept, which could include anything and everything.
I’ve had more performance problems due to hacky workarounds, themselves necessary because of lack of foresight during development, rather than a slow abstraction (in fact, I don’t think I’ve ever seen the latter)
You would think this would encourage better optimized software, but I doubt devs will actually do that. Most modern code practices are about ensuring that code is more easily maintained, often at the cost of performance. Breaking “clean code” rules can easily make programs run 10-25x faster, but will be much harder to maintain.
We also seeing a lot of vibe coding now, which mixes clean code practices (which are well documents online) with messier, less well planned code.
That’s grossly over simplifying the problem. “Clean code” is also not a formally defined concept, which could include anything and everything.
I’ve had more performance problems due to hacky workarounds, themselves necessary because of lack of foresight during development, rather than a slow abstraction (in fact, I don’t think I’ve ever seen the latter)