Recovering interrupter with occasional relapses, lover of spreadsheets, blogger, programmer, adept debugger, conjurer of analogies, and probably other things.
I actually do it because people can only juggle so many concepts at one time, so the early commits representative the first developer trying to get something implemented, without the baggage of years of features and other things added on, so it is very easy to understand and see all of it. Then you can start to see traces of the early program when you look at the current state of a system.
Recovering interrupter with occasional relapses, lover of spreadsheets, blogger, programmer, adept debugger, conjurer of analogies, and probably other things.
This is an interesting approach…see what the earliest intentions to get a sense for "Why did someone toil over this?"
I actually do it because people can only juggle so many concepts at one time, so the early commits representative the first developer trying to get something implemented, without the baggage of years of features and other things added on, so it is very easy to understand and see all of it. Then you can start to see traces of the early program when you look at the current state of a system.
Excellent software archaeology!