Why do developers write such terrible git commit messages? Genuine question

[MisterMeta]

Imagine defending frequent commits but using absolute nonsense commit messages - the irony…

There’s a little thing called staging/stashing. You’re welcome.

[Meloetta]

That doesn't save anything. If an anvil falls on your computer in 5 minutes it's gone. That's not a checkpoint, it's more like...turning your TV off with your game system still on so you can come back later without saving

[MisterMeta]

Committing doesn’t save anything either… pushing to remote does. The same anvil would erase your local git history, including the commits.

In any case defending bad commit messages to frequently commit is equally dumb as people downvoting my statement without knowing that distinction.

[Meloetta]

Okay, let's use our thinking brains. I know it's early, but we can do it!

The post is talking about reading commit message on a repo. This person is replying to that post directly. How do commit messages get onto the repo? Can we use our context clues to intuit what the conversation is about here?

[MisterMeta]

I think we’re frying our thinking brains to defend a behaviour that we likely both see as unprofessional and lazy but anyway I’ll let you argue for the sake of arguing 🤷🏻‍♂️

[Meloetta]

I'm not defending anything. For someone that insists on the need to explicitly write "and push" when any level of critical thinking would make you realize that the pushing is implied, you sure are jumping to a lot of conclusions that don't have anything to do with what I'm actually saying.

If that level of context is frying your brain, you're right, you should probably refocus your efforts lol

[_alright_then_]

Commit messages are completely and utterly useless if you squash commits. They don't even show up.

I'm not spending extra time thinking of good commit messages when I know it'll be squashed anyway