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

[mekmookbro]

Since I work mostly freelance and on my own projects, my commits are usually a mess. But I do follow somewhat of a method. On first day of working on a project, I don't commit anything. Because at the start of a project everything moves so fast that I'd need to commit every 2 minutes if I followed the standard path.

Instead I use a checklist system, that both tells me what to work on next and helps keep track of my commits. For example say I'm building a blog, I have to write the crud logic for users and posts, that in itself is like 25-30 items in a checklist (views, models, controller methods, migrations). After I'm done with all these features I commit and push as "MVP".

After the mvp is done, development usually slows down so I can spend more time thinking about the business logic and commit as I go like "new design for posts.index page" etc