Charles Miller has 6 rules for good unit testing. Click the link for an examplanation of each rule. If you don't know what unit testing is, shame on you (and google it). 

Quote

Six Rules of Unit Testing
Charles' Six Rules of Unit Testing

• Write the test first
• Never write a test that succeeds the first time
• Start with the null case, or something that doesn't work
• Don't be afraid of doing something trivial to make the test work
• Loose coupling and testability go hand in hand
• Use mock objects

One of the most passionately argued schools of thought among software developers is bracing styles. Braces ({ and }) are used in many programming languages to logically segment blocks of code. There is however no exact standard to the use of braces, with the developer free to surround them with as much white space as they like. A good choice of brace formatting can lend itself greatly to the overall readability of a programs source code.

I found an interesting discussion here on the most common forms of brace formatting and the reasons and advocates behind them, and have posted the different styles below.

'K&R style' -- Named after Kernighan & Ritchie, because the examples
in K&R are formatted this way. Also called `kernel style' because the
Unix kernel is written in it, and the `One True Brace Style' (abbrev.
1TBS) by its partisans. In C code, the body is typically indented by
eight spaces (or one tab) per level, as shown here. Four spaces are
occasionally seen in C, but in C++ and Java four tends to be the rule
rather than the exception.
 
if () {  
   
'Allman style' -- Named for Eric Allman, a Berkeley hacker who wrote a
lot of the BSD utilities in it (it is sometimes called `BSD style').
Resembles normal indent style in Pascal and Algol. It is the only style
other than K&R in widespread use among Java programmers. Basic indent per level shown here is eight spaces, but four (or sometimes three)
spaces are generally preferred by C++ and Java programmers.
 
if ()
{           
 
'Whitesmiths style' -- popularized by the examples that came with
Whitesmiths C, an early commercial C compiler. Basic indent per level
shown here is eight spaces, but four spaces are occasionally seen.
 
if ()
        {            
   
'GNU style' -- Used throughout GNU EMACS and the Free Software
Foundation code, and just about nowhere else. Indents are always four
spaces per level, with `{' and `' halfway between the outer and inner
indent levels.
 
if ()
  {

The style I tend to use is Allman, mainly because Visual Studio nicely forces this format upon me by default. It must be a Microsoft thing. Apparantly Whidbey (Visual Studio 2005) will let you choose what code formatting styles it applies to your code.