Coveros

Most of us like things done the right way and (more often than not) our way.   Nothing can be more infuriating than looking through poorly documented logs or code, and trying to understand poor documentation and what it was meant to get across.

During development we often look to setting up good coding practices that include documenting and commenting what’s going on and in what format we agree to write comments.  And in many organizations, this is where keeping those good practices stop.  In most organizations I’ve worked for, developers rarely submit good, formatted notes with their code if they submit documentation at all.   So here is a quick and simple method to enforce good commenting standards for your organization using SecureCI.  If you haven’t downloaded SecureCI, this is your time to try it out!

Example Development Process

When I’m looking through SVN logs for a specific revision I like to know that the information in the log is going to let me know everything I need to know to successfully revert my repository to the correct revision.    I want to know that whenever a developer submits code that it can be tracked back to a specific ticket in Trac.  The best way to do this is with a simple Pre-Commit Check.
Read the rest of this entry »