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”>

Three Internet Companies, Three Stories

LA Weekly: Do You IMDB?. IMDB continues to be the number one site I go to for movie knowledge. They groked hypertext early on and the way they designed their site, tieing metadata between movies together with hyperlinks, was a major example for others to follow.

SFGate: CRAIGSLIST On the record: Craig Newmark. Most of you know that craigslist has recently been invested in by eBay, but for those that don’t, this is a good read.

Salon: Blogging grows up: The story of Mena and Ben Trott’s Movable Type, and Six Apart, the company they founded around it. A must read for content tool developers.