Incorporate recommendations from Jethro

[lorddev]

From Jethro Larson:

Write good commit logs that state what was changed and link to issue trackers. Don't mix spaces and tabs! Don't over plan, don't over document, don't over engineer, yagni, kiss, make it work without js first; write the manual first; Code like you're designing an API; start with the user experience not the db; know the page lifecycle; understand the waterfall; make everything non-blocking; don't forget the robots

[lorddev]

From 37signals: "Getting real starts with the interface, the real screens that people are going to use. It begins with what the customer actually experiences and builds backwards from there. This lets you get the interface right before you get the software wrong."