3 ms·
The canonical case in software teams is arguing about code style guidelines. Almost never do the structural elements of good code organization get discussed. I
by hinkley 5y ago
The canonical case in software teams is arguing about code style guidelines.
Almost never do the structural elements of good code organization get discussed. Instead we wrap around the axle arguing about things like bracket placement and whitespace. Usually in a manner which damages team cohesiveness rather than building it.
- denton-scratch 5y agoBut, but, but: bracket placement and whitespace matter! It's a real drag to have to edit a piece of code in which the conventions for brackets and space are all over the place. It doesn't matter what conventions you adopt. But not adopting any creates unnecessary friction.
- hinkley 5y agoYes, they do matter, but not as much as using accurate words for things. I know people who use the same noun or adjective for four incompatible concepts in their code. Buy a goddamned thesaurus, or use a free one online. It’s okay to reach out for help on things you struggle with instead of making the rest of of us suffer. You can reduce the white space conversation to picking a good code formatted. But no formatted is going to fix your nightmare code that you claim is “self documenting”. Fuck that guy. Or better, fire him. Get that weak sauce outta here.