10 ms·
I got some flak at a prior job for saying I had some quibbles with clean code (a few years after I had read it), and I'm glad this opinion is more popular today
by hughesjj 2y ago
I got some flak at a prior job for saying I had some quibbles with clean code (a few years after I had read it), and I'm glad this opinion is more popular today. There's so much cargo culting hype with "best practices" and style, I hate it. Same with how overly dogmatic people were with OOP paradigms when it came out (remember using anonymous interfaces to pass a function around in java?). Same with the functional backlash to that.
It's fun and enlightening to go ham on any particular style/framework/philosophy, but actually living by dogma in prod gets kinda dangerous and imo is counter to the role of a senior+ engineer
- AtlasBarfed 2y agoThe very term "best practice" is such a loaded term. It implies: 1) empirical measurement compared to a large number of alternatives ... the empirical measurement or study is never mentioned: because they do not exist 2) the best practice is valid in all measurements and criteria of comparison: performance, elegance, simplicity, correctness 3) since there is no data, the reasons for why the practice was designated best are rarely even explained 4) nor are the circumstances or individual or source of "best practice" detailed 5) it will always be the best practice: it is the BEST! It CANNOT be improved. So we have an unsubstantiated, unargued, unsourced, non-authoritative, exaggerated declaration in virtually every case of "best practice"
- answerheck 2y agoCopy that. CC has done a lot of harm in some ways.