Read This: The Three Rs of of Clean Code

I won’t guild this with more than an economy of words can describe.  Do you code?  Do you make money by cutting and selling code?  Great.  I imagine you also believe that you may be doing some really high quality work.

Chances are, in reality, you’re not.  So what to do?  Write a set of guidelines into a style manual and force everyone to use it?  Not very successful.  How about treating your teams like the professionals they are and giving them rules to live by?  Michael Norton did just that with a team he coached.

Read.  This.

The Three "R"s of Clean Code

Too busy?  Fine.  I’ll extrapolate the key points:

Follow the Boyscout Rule

• Leave code better than you found it.

Readable

• Descriptive function names
• Small functions
• Few comments
• Few arguments

Reliable

• Tested
• Descriptive function names
• Necessary code

Responsible

• Single responsibility principle
• Necessary code
• Tested