[majormajor]

> I've worked for 10 years across 20 different commercial codebases. None of this stuff about writing good commit messages really matters. No one reads old commits. The "truth" is what the current code is doing and it doesn't really matter how it got there.

> I'm sure someone will say "but I use the history ALL THE TIME to source dive and paragraphs of context are super helpful". This is not the case for 95% of developers or projects so I can't really endorse spending time learning this "best practice".

> It's fine to be aspirational, but it's such a shame if people see posts like this and think they are failures or "bad" developers or that this is a widespread practice.

I'm that person who's often digging into the history.

It's often to understand other things that the people writing poor messages were sloppy about.

So sure, focus more on writing good code than writing good messages but the truth is that the context of the code and the feature will change over time so preserving the original context you had in your head when you wrote it is super valuable when the next poor sap has to come along a year later and change it.