Writing good code and writing good commits definitely clusters together. It's part of a general pride in quality of work, organization, and planning. Going bac

Writing good code and writing good commits definitely clusters together. It's part of a general pride in quality of work, organization, and planning. Going back into the commit history can be useful to figure out if something suspicious was introduced intentionally or if it was just a mistake. Beyond about 3-6 months, the author will generally not have any context to remember small code details, so leaving breadcrumbs for your future self and team can be nice.