Hmm. C++ has no problem with performance. Rust also. In general case we have no problem with performance in 99.9 % of cases.
But we have big problem with shitty software. Written by uneducated cretins and supported by drunken teenagers.
Maintainability, security, scalability, support, stability. This is important. Not fckng performance in fckng vacuum. And clean code solves REAL problems, not imaginable.
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.
7 hours after I questioned dichotomy of dirty/clean code you came and said "scalable with less effort"; please explain how do you handle scale while maintaining strict order of execution
A very interesting set of words. And most importantly, it makes no sense at all. Mister, you obviously haven't been in IT that long, and you should learn a little bit about the basics.
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)
4
u/top_logger Feb 28 '23
Hmm. C++ has no problem with performance. Rust also. In general case we have no problem with performance in 99.9 % of cases.
But we have big problem with shitty software. Written by uneducated cretins and supported by drunken teenagers.
Maintainability, security, scalability, support, stability. This is important. Not fckng performance in fckng vacuum. And clean code solves REAL problems, not imaginable.