- Local time
- Yesterday, 19:24
- Joined
- Feb 28, 2001
- Messages
- 30,007
After a while, I settled for "paragraph" comments at the beginning of any sequence. But if there was any crucial moment where an answer had been developed, I demanded that it get a special comment.
I also told my people that we would have a project "bible" - which we did - to tell us what we had agreed to do in any section, and the rule was that a design change that altered the description of the section (as opposed to bug fixes that didn't change intent) HAD to be reviewed by the group for understanding and agreement that it was (a) effective and (b) necessary or at least appropriate. Bug fixes, we could make and just document in code and in a patch history document.
In retrospect, I wasn't as nice to my team back then as I might have been. However, I stayed friends with all but one of them.
I also told my people that we would have a project "bible" - which we did - to tell us what we had agreed to do in any section, and the rule was that a design change that altered the description of the section (as opposed to bug fixes that didn't change intent) HAD to be reviewed by the group for understanding and agreement that it was (a) effective and (b) necessary or at least appropriate. Bug fixes, we could make and just document in code and in a patch history document.
In retrospect, I wasn't as nice to my team back then as I might have been. However, I stayed friends with all but one of them.