If you’re focused on what character of “GitHub” or “oauth” should capitalised in a variable name, then you really are focusing on the wrong problems of software development.
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.
If the author really cares this much then they should be linter rules instead of a blog post.
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.
Just write a linter rule and be done already.
```suggestion
my_change
```
if there's someone on your team prone to style nitpicks like this, this can often sate them, and it's convenient for you to merge into your branch