Fork Of
Revisions
-






25cc3d
timocratic
Mon Dec 22 13:30:47 -0800 2008
-






f4063b
timocratic
Mon Dec 22 13:30:21 -0800 2008
-






124d0b
timocratic
Mon Dec 22 13:22:21 -0800 2008
-






1f9d03
timocratic
Mon Dec 22 13:21:40 -0800 2008
-






b2b806
timocratic
Mon Dec 22 13:21:23 -0800 2008
-






aeaa01
timocratic
Mon Dec 22 13:16:23 -0800 2008
-






516556
timocratic
Mon Dec 22 13:15:11 -0800 2008
-






562918
timocratic
Mon Dec 22 13:14:04 -0800 2008
-






b8b2a3
timocratic
Mon Dec 22 13:13:04 -0800 2008
-






65a767
timocratic
Mon Dec 22 13:12:38 -0800 2008
Every gist with this icon (
Every repository with this icon (
Note to Self
Test
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
If it's happened more than twice, don't ever do it by hand again.
Queue
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.
Model Statefully
If there's a lifecycle, model it as a real state machine. Beware ad hoc flags.
Simplify
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.
Enforce consistency
Coding conventions and consistency help productivity.
Update (but not too early)
Keep frameworks, plugins, libraries, and tools up-to-date, but think twice before using a production app to play with the bleeding edge.
Measure
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?
Refactor
If it's broken, fix it, not just superficially.


