title: Besides "treat warnings as errors" and fixing memory leaks, what other ideas should we implement as part of our coding standards?
body: <p>First let me say, I am not a coder but I help manage a coding team.  No one on the team has more than about 5 years experience, and most of them have only worked for this company.. So we are flying a bit blind, hence the question.</p>
  
  <p>We are trying to make our software more stable and are looking to implement some "best practices" and coding standards.  Recently we started taking this very seriously as we determined that much of the instability in our product could be linked back to the fact that we allowed Warnings to go through without fixing when compiling.  We also never bothered to take memory leaks seriously enough.  </p>
  
  <p>In reading through this site we are now quickly fixing this problem with our team but it begs the question, what other practices can we implement team wide that will help us?   </p>
  
  <p>Edit: We do fairly complex 2D/3D Graphics Software that is cross-platform Mac/Windows in C++.</p>