I've started doing microcommits recently which helped with that exact issue highlighted in the article. My current workflow, on a side project as a solo develop

I've started doing microcommits recently which helped with that exact issue highlighted in the article. My current workflow, on a side project as a solo developer, is to commit as soon as I have any relevant piece of functionality (even if it's just an empty React component that I'll then build out) which also makes it trivial to come up with a commit message. When a feature is done (or part of the feature if it's big enough already) I create a PR which I briefly review. Not as deeply as I would with an unknown code, just want to make sure there's nothing obviously wrong. While an unrelated refactoring is still bundled in the same PR, it doesn't matter because it's a separate commit and I rebase/fast-forward into master.