Content
@
0 reply
0 recast
2 reactions
grin
@grin
what's some programming advice that's considered common sense or that you hear often, but is actually bad advice?
18 replies
7 recasts
16 reactions
timdaub
@timdaub.eth
- comment your code - be consistent
1 reply
0 recast
0 reaction
MOLO
@molo
this is bad advice?
1 reply
0 recast
1 reaction
timdaub
@timdaub.eth
yes
1 reply
0 recast
0 reaction
MOLO
@molo
hmm. why?
1 reply
0 recast
1 reaction
timdaub
@timdaub.eth
Comments: Never explain what your code does in comments. Only write them when you want to persist info that hasn't already been expressed in code (e.g. context) Consistency: Inconsistency makes people feel bad. Your code still runs. It's emotional/irrational to write consistent code, just bc it makes you feel better
3 replies
0 recast
0 reaction
alex
@alexgrover.eth
consistency can be important in the context of a (larger) team like most things, there’s lots of nuance here, but the blanket statements sure are good engagement bait 😂
1 reply
0 recast
1 reaction
timdaub
@timdaub.eth
Your consistency is my inconsistency. Consistency isn't objective
2 replies
0 recast
0 reaction
grin
@grin
bro, you Feyerabend?
0 reply
0 recast
1 reaction
alex
@alexgrover.eth
there are objective measures that fall under that label though. for example requiring people to use the same language or data store. At some point you can even quantify dev velocity for more subjective measures as well. I’m sure google and Facebook understand very well how much code style guides impact the business
1 reply
0 recast
0 reaction
