I work on several legacy codebases which were: - written by people who were not me - written by people who have since left the company - the original documen

I work on several legacy codebases which were: - written by people who were not me - written by people who have since left the company - the original documentation has rotted away through wiki replacements, issue tracker replacements, or being lost via people turnover or system replacement. The result in many cases is the code is the _only_ documentation of the system behaviour, so seeing what was introduced together is important context to understanding why it is the way it is. I probably run git blame more than git commit at this point and there's a real QoL difference between the good commit messages and the "changes for ticket12345" commit messages.