> I don't necessarily think that's "I'm right, you're wrong". Instead it looks more like just being strongly opinionated on the matter.
Are you honestly making the claim that the part of the post that repeatedly states "You're doing it wrong" isn't saying "I'm right you're wrong", but rather just being "strongly opinionated on the matter?"
It reads very tongue in cheek to me because I have gone on those types of rants in the past. And I've known a number of other people who hold similar stances and they also do the same thing.
Like I've literally gone on a "if you do X you are doing it wrong" rant about git verbatim when trying to explain patchset etiquette in the past. It's not trying to say "you are always wrong for doing it this way", it's just way too long winded and difficult to explain your point about should be versus shouldn't be done in your view while being nuanced and pointing out that they are sometimes okay. You just say "if you are doing X you are wrong" and hope the reader picks up on the subtext that you are just making a point and not trying to be authoritative. It's a lot easier to do in person but alas.
> Every software team in the world has its own culture and ways of doing things, which is all good but when I see teams using git as a glorified `ctrl + s` it really breaks my heart.
>
> This should be its own blog post (one I’m planning on writing) but these are some of my general issues with how I see teams use git. I apologise in advance for any hurt feelings but here goes…
It's not "I'm right, you're wrong", it's hyperbole. They are using an exaggeration to drive home a point and at the same time making that point in a more concise manner.
Maybe instead of saying "you are doing it wrong" you could say "you are underutilising git" but even then that only applies to some of the things he listed and not others. Hence it's easier to express that what you are saying is your opinion and then use hyperbole (i.e. "you are doing it wrong") to make a concise point.
The OP does this prior to going into their list of gripes:
> This should be its own blog post (one I’m planning on writing) but these are some of my general issues with how I see teams use git. I apologise in advance for any hurt feelings but here goes…
It's only them definitively claiming that "I'm right and you are wrong" when taken out of context from the surrounding article text. But within the context of that article, it's just a use of hyperbole to make a concise point.
I don't necessarily think that's "I'm right, you're wrong". Instead it looks more like just being strongly opinionated on the matter.
As someone who is very opinionated on git and VCS in general, I get it. The difference in experiences between projects with good, clean, descriptive git histories (see most projects that follow the linux kernel/git patchset approach), projects with linear PR squash histories, and projects with lots of useless "fixup", "fix", "try again" type commits is utterly and entirely massive.
It's the type of gripe that I personally would place alongside projects not having good unit testing. A project can still be workable without them but I'm going to fight like hell to get things fixed up so we can move fast in the long run.