How all of this hangs together

Many software problems can be avoided by following the Software rules (naming conventions, coding style) Why rules ?? Because 13 sub-systems software (and probably x10 different style) need to talk to each other ... http://www.star.bnl.gov/STAR/comp/train/standards.html http://www.star.bnl.gov/STAR/comp/train/NamingAdvice.txt
New code follows a peer review process Ensures early compliance check May be regularly scheduled by sub-system (software decay) http://www.star.bnl.gov/STAR/comp/sofi/peer-review.html
To be created A set of examples of cosing styles and structure to avoid (common mistakes and pitfalls)
It is a good idea to read those documents even if private code ...

New code follows a peer review process Ensures early compliance check May be regularly scheduled by sub-system (software decay) http://www.star.bnl.gov/STAR/comp/sofi/peer-review.html