>how often is "understanding your project history" something that actually comes up for you? Frequently, for any long and complex project. Large amounts were

>how often is "understanding your project history" something that actually comes up for you? Frequently, for any long and complex project. Large amounts were written by people no longer working on it, and the history of how things came to be can help fill in documentation gaps and make intent clear. By "frequently" I mean something like "I check history for about 2/3rds of bug fixes, and 1/4 of adding features" to understand the surroundings better, when writing or reviewing. Anything that makes that better saves me hours per week. It catches and prevents more than enough subtle issues to be worth the effort.