Hacker News Reader

There is value in having local consistency, which is usually achieved through having rules.

The more uniform a code base, the easier it is to breeze around and get stuff done. Naming things is already hard, so having rules around the annoying bits is nice.

View on HN

Rules are best handled by automated tools with as few configuration options as possible - like gofmt or black.

This way people won't start bikeshedding about the placement of curly braces, they either accept the style or move on.

It also prevents things from getting political or personified. It's the tool that's making the decisions, not a specific person.

This is why I push for gofumpt over gofmt

These rules aren’t really about naming things, which I agree is hard. It’s pedantry around terms that really don’t matter which way you choose and thus are categorically not “best practices” let alone “idioms” one must abide by.

If the author really cares this much then they should be linter rules instead of a blog post.

Reply on news.ycombinator.com