3 ms·
Sometimes when working on an old code base built by developers that came and went, one needs to perform what I call "code archeology": going back in time to und
by nicolaslem 3y ago
Sometimes when working on an old code base built by developers that came and went, one needs to perform what I call "code archeology": going back in time to understand why a feature was implemented the way it was.
Whether this is feasible at all depends largely on the care developers put in structuring their commits.
- ohwellhere 3y agoYes! The source code is itself the first level of documentation. The commit history is the second. A free form textual interface to document everything about why you made the changes you just made? Why not maximize the value of this resource!
- Izkata 3y agoThis has become a large chunk of my job over the past few years, as part of fixing/upgrading systems no one has touched in a decade, and none of those original people are still here. There are some weird things in there I've only been able to figure out because all the svn history still exists.