2 ms·
Source control history is absolutely essential for me for debugging hard-to-reproduce bugs. The first step is a blame (both git and svn have this) to find out w
by flohofwoe 7y ago
Source control history is absolutely essential for me for debugging hard-to-reproduce bugs. The first step is a blame (both git and svn have this) to find out when the last changes to a suspicious piece of code happened and what has changed. Also who changed it so I know who to talk to (if they are still in the company). If the commit comment gives additional info, why the change happened that's great.
Sometimes those changes are over a decade old (of course such old changes make it more unlikely that they are still buggy, but new changes may interact with those old changes in unexpected ways).
So yes, the older a code base, the more important a complete change history becomes.