becoming a better coder...

things that might help you become a better coder

[Dont repeat yourself][1]

[Command-query separation (CQS)][2]

[Defensive programming][3]

[S.O.L.I.D.][4]

[Code Smell][5]

[Smells to Refactorings][6]
Patterns & Anti-Patterns

[Software Craftsmanship][7]

[Testable code drags OOP into Functional Programming][8]
[Writing Testable Code][9]
[How to Write 3v1L, Untestable Code][10]
[Design by Contract][11]

[1]: http://en.wikipedia.org/wiki/Don't_repeat_yourself
[2]: http://en.wikipedia.org/wiki/Command-query_separation
[3]: http://en.wikipedia.org/wiki/Defensive_programming
[4]: http://mmiika.wordpress.com/oo-design-principles/
[5]: http://en.wikipedia.org/wiki/Code_smell
[6]: http://www.industriallogic.com/papers/smellstorefactorings.pdf
[7]: http://en.wikipedia.org/wiki/Software_Craftsmanship
[8]: http://noss.github.com/2009/02/21/testable-code-drags-oop-into-functional-programming.html
[9]: http://googletesting.blogspot.com/2008/08/by-miko-hevery-so-you-decided-to.html
[10]: http://googletesting.blogspot.com/2008/07/how-to-write-3v1l-untestable-code.html
[11]: http://en.wikipedia.org/wiki/Design_by_Contract