jbarnette · December 18, 2008 22:54 · Jan 7, 2009 · Jan 7, 2009 · Jan 7, 2009 · Dec 22, 2008
diff --git a/think.markdown b/think.markdown
@@ -8,7 +8,7 @@ consequences.
 
 ## Be Lazy
 
-If it's happened more than twice, don't ever do it by hand again.
+Write tools. If it's happened more than twice, don't ever do it by hand again.
 
 ## Be Asynchronous
 

diff --git a/think.markdown b/think.markdown
@@ -27,7 +27,7 @@ simplicity takes a bit longer, but it'll pay off.
 
 ## Be Consistent
 
-Inconsistent file names, task names, or coding styles hurt productivity.
+Inconsistent file names, task names, and coding styles hurt productivity.
 
 ## Be Timely (but not too timely)
 

diff --git a/think.markdown b/think.markdown
@@ -27,7 +27,7 @@ simplicity takes a bit longer, but it'll pay off.
 
 ## Be Consistent
 
-Inconsistent file names, task names, or coding conventions hurt productivity.
+Inconsistent file names, task names, or coding styles hurt productivity.
 
 ## Be Timely (but not too timely)
 

diff --git a/think.markdown b/think.markdown
@@ -12,8 +12,9 @@ If it's happened more than twice, don't ever do it by hand again.
 
 ## Be Asynchronous
 
-If it can be done outside the request/response cycle, defer it.
-Mailers, uploads, audit trails.
+If it can be done outside the request/response cycle, consider queuing it.
+Mailers, uploads, audit trails, anything with an external system dependency
+or a lot of IO.
 
 ## Be Stateful
 

diff --git a/think.markdown b/think.markdown
@@ -1,4 +1,4 @@
-# Lessons Learned
+# Note to Self
 
 ## Be Confident
 

diff --git a/think.markdown b/think.markdown
@@ -44,7 +44,6 @@ Find the root cause. Keep asking **why**, even when you're tired and under
 the gun. The guesswork patch you write today will be a nightmare tomorrow.
 
 ## Be Wrong
-
-Dogma is for theorists. If it's not working, change it, no matter how long
+If it's not working, change it, no matter how long
 it took to write. Don't throw good money after bad. Admit mistakes early
 and often.
diff --git a/think.markdown b/think.markdown
@@ -12,7 +12,7 @@ If it's happened more than twice, don't ever do it by hand again.
 
 ## Be Asynchronous
 
-If it can possibly be done outside the request/response cycle, defer it.
+If it can be done outside the request/response cycle, defer it.
 Mailers, uploads, audit trails.
 
 ## Be Stateful

diff --git a/think.markdown b/think.markdown
@@ -1,4 +1,4 @@
-# Hard Lessons
+# Lessons Learned
 
 ## Be Confident
 

diff --git a/think.markdown b/think.markdown
@@ -1,3 +1,5 @@
+# Hard Lessons
+
 ## Be Confident
 
 Tests build confidence. Write 'em. They'll save your ass, and they'll

diff --git a/think.markdown b/think.markdown
@@ -20,7 +20,7 @@ If there's a lifecycle, model it as a real state machine. Beware ad hoc flags.
 ## Be Clear
 
 You'll write it once, but you'll read it a lot. Code accordingly. Sometimes
-simplicity takes a bit longer, but it'll pay off rapidly.
+simplicity takes a bit longer, but it'll pay off.
 
 ## Be Consistent
 

diff --git a/think.markdown b/think.markdown
@@ -17,7 +17,7 @@ Mailers, uploads, audit trails.
 
 If there's a lifecycle, model it as a real state machine. Beware ad hoc flags.
 
-## Be Simple
+## Be Clear
 
 You'll write it once, but you'll read it a lot. Code accordingly. Sometimes
 simplicity takes a bit longer, but it'll pay off rapidly.
@@ -40,3 +40,9 @@ Is that code really faster? Do users really want that feature?
 
 Find the root cause. Keep asking **why**, even when you're tired and under
 the gun. The guesswork patch you write today will be a nightmare tomorrow.
+
+## Be Wrong
+
+Dogma is for theorists. If it's not working, change it, no matter how long
+it took to write. Don't throw good money after bad. Admit mistakes early
+and often.
diff --git a/think.markdown b/think.markdown
@@ -39,4 +39,4 @@ Is that code really faster? Do users really want that feature?
 ## Be Persistent
 
 Find the root cause. Keep asking **why**, even when you're tired and under
-the gun. The temporary patch you write today can be a nightmare tomorrow.
+the gun. The guesswork patch you write today will be a nightmare tomorrow.
diff --git a/think.markdown b/think.markdown
@@ -1,12 +1,14 @@
-## Test It
+## Be Confident
 
-Write tests. They'll save your ass.
+Tests build confidence. Write 'em. They'll save your ass, and they'll
+let you take a chainsaw to your code without being afraid of unintended
+consequences.
 
-## Automate It
+## Be Lazy
 
 If it's happened more than twice, don't ever do it by hand again.
 
-## Queue It
+## Be Asynchronous
 
 If it can possibly be done outside the request/response cycle, defer it.
 Mailers, uploads, audit trails.
@@ -22,9 +24,19 @@ simplicity takes a bit longer, but it'll pay off rapidly.
 
 ## Be Consistent
 
-Inconsistent file names, task names, or code hurts productivity.
+Inconsistent file names, task names, or coding conventions hurt productivity.
 
 ## Be Timely (but not too timely)
 
 Keep frameworks, plugins, libraries, and tools up-to-date, but think twice
 before using a production app to play with the bleeding edge.
+
+## Be Certain
+
+Don't speculate, get data. Act on what you know, not what you suspect.
+Is that code really faster? Do users really want that feature?
+
+## Be Persistent
+
+Find the root cause. Keep asking **why**, even when you're tired and under
+the gun. The temporary patch you write today can be a nightmare tomorrow.
diff --git a/think.markdown b/think.markdown
@@ -1,30 +1,30 @@
-# Test It
+## Test It
 
 Write tests. They'll save your ass.
 
-# Automate It
+## Automate It
 
 If it's happened more than twice, don't ever do it by hand again.
 
-# Queue It
+## Queue It
 
 If it can possibly be done outside the request/response cycle, defer it.
 Mailers, uploads, audit trails.
 
-# Be Stateful
+## Be Stateful
 
 If there's a lifecycle, model it as a real state machine. Beware ad hoc flags.
 
-# Be Simple
+## Be Simple
 
 You'll write it once, but you'll read it a lot. Code accordingly. Sometimes
 simplicity takes a bit longer, but it'll pay off rapidly.
 
-# Be Consistent
+## Be Consistent
 
 Inconsistent file names, task names, or code hurts productivity.
 
-# Be Timely (but not too timely)
+## Be Timely (but not too timely)
 
 Keep frameworks, plugins, libraries, and tools up-to-date, but think twice
 before using a production app to play with the bleeding edge.
diff --git a/think.markdown b/think.markdown
@@ -0,0 +1,30 @@
+# Test It
+
+Write tests. They'll save your ass.
+
+# Automate It
+
+If it's happened more than twice, don't ever do it by hand again.
+
+# Queue It
+
+If it can possibly be done outside the request/response cycle, defer it.
+Mailers, uploads, audit trails.
+
+# Be Stateful
+
+If there's a lifecycle, model it as a real state machine. Beware ad hoc flags.
+
+# Be Simple
+
+You'll write it once, but you'll read it a lot. Code accordingly. Sometimes
+simplicity takes a bit longer, but it'll pay off rapidly.
+
+# Be Consistent
+
+Inconsistent file names, task names, or code hurts productivity.
+
+# Be Timely (but not too timely)
+
+Keep frameworks, plugins, libraries, and tools up-to-date, but think twice
+before using a production app to play with the bleeding edge.