3 ms·
> reading the commit messages, to understand why it was done that way. that's assuming the original authors used version control, committed often enough to lea
by TheJoYo 8y ago
> reading the commit messages, to understand why it was done that way.
that's assuming the original authors used version control, committed often enough to leave meaningful commit messages, and bothered to explain their decisions.
pretty much every code base i've taken over in my current role have consisted of a single posting commit with zero documentation.
- james-skemp 8y agoGiven the context, I think the individual that you're quoting said that because they did do that within the commit messages. And outside of the one place where I was the person to introduce source control to the organization, I've found commit messages to be pretty telling. Most developers tend to let their feelings pop out in their commit messages, and too when and how often they're committing. In your particular case, sounds like either a junior developer, legacy systems, or a sole developer.