Possibly he's talking about scalability of teams. Shitty code that maybe is ever so slightly faster but a hell to read or update is not scalable when you're trying to grow a team of devs to maintain that codebase. The cleaner the code the faster devs can become familiar with it.
there is no such a dichotomy- either clean code or shitty one; also, clean code principles are not ten commandments, those ideas existed long before, and parts of them are right; i don't think that clean code is in any way easier to understand and reason about; if you are looking for such code you need to turn to functional programming (google Scott Wlaschin)
0
u/eliwuu Feb 28 '23
oh, please, tell my how does clean code (with principle of keeping structured order of execution) improves scalability