3 ms·
I don't understand this claim of readability. If it were true, then you wouldn't be able to read a code base with a different code style. In truth, the switch t
by aero142 6y ago
I don't understand this claim of readability. If it were true, then you wouldn't be able to read a code base with a different code style. In truth, the switch takes about 10 seconds for me to get used to. Which is about 10,000 times less that the time I've wasted debating code style with other developers that insist that "consistency" is a useful goal without justification.
There is exactly one concrete goal that I have found. Keeping people's editors from fighting each other in editing the same file. Other than that, just let it go. I've switch everything I can find to the automated formatters so that I never have to listed to someone complain about formatting again.
- t-writescode 6y agoCognitive load is real and that 10 seconds is more load you have to put onto your mental ram to get anything done. It’s easy to not notice it until it’s not. That’s why autoformatters are better in general. There’s no argument, it’s just how it is, and it’s dealt with.
- psyc 6y agoI have no problem diving into a new code base on a new team with a style that’s unfamiliar. I absolutely do not want to switch styles as I work on the same project. I don’t much care what the style is. Successful implementations I’ve seen include: tasking one person to pick a style, then allowing exactly one meeting in which to iron out the quibbles. Or, literally googling for a style recommendation and just choosing one of the top results, as is, no discussion. I agree that the endless religious arguments must be avoided. All the more reason to seek a strong manager and / or tech lead.