Before you code, think.I think this is pretty obvious. It's always advised to have a conceptual blue-print of your program before you start implementing it.
Before you write, read.This one is a bit ambiguous--read what, exactly? The code can't be read if it is not written.
Before you comment, reflect.Mmm, this is a hard one. I'd say if you're working on a group project, then this is absolutely substantial. Don't get the wrong idea here: reflecting on self-written code is good practice, though reflecting too much might guarantee more un-needed, trivial comment than code, and that is not what you want.
Before you release, test.Touche!
You aren't the only one :P