4 ms·
> If they didn't write a git commit message because "no one is going to read it anyway", they're a lazy engineer. If an engineer spends an hour writing a commi
by qez2 3y ago
> If they didn't write a git commit message because "no one is going to read it anyway", they're a lazy engineer.
If an engineer spends an hour writing a commit message that no one reads, that's an unproductive engineer, compared to where they should be.
I have to admit, I am lazy. I don't spread seeds by hand; I use a tractor. I don't swim across the ocean; I use an air plane. Likewise, I don't write documentation in commit messages; I write documentation in PR descriptions, READMEs, and official document sources. You got me, I'm incompetent.
My "job" is to write software, not follow some arbitrary "pure" practices.
> If a coworker doesn't understand a code change, because they didn't bother to read the commit message
And I would argue we shouldn't cater to developers who make documentation difficult to access for everyone else by hiding it where only crappy tools can reach it.
- mtrower 3y ago> If an engineer spends an hour writing a commit message that no one reads, that's an unproductive engineer, compared to where they should be. Okay, maybe don't spend an hour. It would take a special kind of commit to need more than a few minutes writing a decent commit message. > And I would argue we shouldn't cater to developers who make documentation difficult to access for everyone else by hiding it where only crappy tools can reach it. Yeah. Like web browsers. And PDF viewers. The non-caustic point here is that clearly different people have different ideas about what is accessible.