Why Your Code Sucks

Dave Astels posted a concise checklist to determine if you code sucks. Memorize it:

1. Your code sucks if it doesn’t work.
2. Your code sucks if it isn’t testable.
3. Your code sucks if it’s hard to read.
4. Your code sucks if it’s not understandable.
5. Your code sucks if it dogmatically conforms to a trendy framework at the cost of following good design/implimentation practices.
6. Your code sucks if it has duplication.

Three books on my to read list

And people wonder why it takes me ages to return a book….

java.net: JJGuidelines: “a set of conventions and guidelines for java and J2EE related development.’

TSS: Java Testing and Design: “how to understand what application you want to write, what strategies are likely to get you there, and then how to measure your level of success.”

TSS: The J2EE Architect’s Handbook: “is written for technical architects and senior developers tasked with designing and leading the development of J2EE java applications”>