3 ms·
But something like gofmt is valuable. If you're removing unused imports and similar with every time you write source to disk, you gain a ton of benefits (especi
by zamalek 5y ago
But something like gofmt is valuable. If you're removing unused imports and similar with every time you write source to disk, you gain a ton of benefits (especially in VCS history).
Otherwise, totally, coding standards and so forth are just bike shedding.
- nomoreplease 5y ago> coding standards Coding standards for NASA certainly isn’t bike shedding, especially if they focus on reliability or security
- zamalek 5y agoNASA effectively enforces a DSL, not coding standards.
- joshribakoff 5y agoCode formatting, quality metrics, and style guide/standards are all different things.
- ris 5y agoExcept gofmt and many others make the single most boneheaded formatting mistake - aligned indents. Aligned indents will cause a single-line change to balloon into a many-line diff, solely to re-align with the new content's length. This causes all sorts of unnecessary merge/rebase conflicts.
- dewey 5y agoIn my years of working with Go in multiple teams that was never really a problem and I haven't even thought about that once so far.
- ris 5y agoI wonder to what extent you've had to maintain stable branches then. Still, if people are going to enforce something as meaningless as formatting, why not at least get it right? Otherwise it's unarguably just about stroking the obsessive compulsive tendencies of the team members who are more that way inclined.