The Code Management/Configuration Management working group at FNAL was given a charge, which I have parsed to distinguish software and management problems. The group has issued its report, and its recommendations are implemented.
Our program development model leaves something to be desired in terms of reliability. I wrote a proposal (HTML) for using Code Godfathers (PostScript 128K 11-Oct-1995), which proposes procedures closer to industrial code development ones. I air my dirty laundry (PostScript 68K 30-Jun-1995). LaTeX sources for the CDF reports mentioned above live over here .
Consider the following cautionary tale as a warning that OO-design is addicting. And, of course, we trust each other .
Some interesting thoughts on computer language nature and use among other things.
Here's my condensation of Structured Walkthroughs by Edward Yourdan, together with some comments on how this does or does not apply to our situation at CDF. FNAL has since instituted some walk-through procedures, which I'll link to as soon as I find them.
Try this YBOS help and intro page showing routines people actually use and illustrating common bugs.
I have some older notes, many of which are now rendered obsolete by events and decisions.