Re:How to Build Good Software
by skybrian on Monday August 19, 2019 @01:06PM
(#20739536)
Yes, I agree that treating most documentation as project history is the practical way to go.
Another thing that helps is to write good commit messages giving the business context for a change. When code is reviewed, the commit messages should be reviewed as well. If they don't agree then that's a problem.
Another thing that helps is to write good commit messages giving the business context for a change. When code is reviewed, the commit messages should be reviewed as well. If they don't agree then that's a problem.