Re:Good Software Development Habits
by stoperaticless on Sunday November 17, 2024 @06:43PM
(#42168375)
Whats wrong with tooling enforcing it?
I mean, where you wrap is not important, and is best left to tooling (brain cycles and meeting time can be used for more important things)
Cluttering up git line annotations and code reviews with people's dev envs fighting over where to wrap lines or whether there's a space after parens or whatever is a waste of everyone's time and an impediment to seeing the actual code changes. That's why tooling should enforce a format, not because there's particular importance to the exact enforced format.
This "it's more important to wrap your code at 80 columns than to understand how the cache hierarchy works" stuff is becoming worryingly endemic. Teamscale has built an entire business around fooling nontechnical managers into believing this shit is not only worthwhile, but should be enforced by tooling, and middle managers at FAANGs, who should know better, are starting to buy in.