|
From: Ali M. <ali...@gm...> - 2005-06-14 04:36:16
|
Hey there, I'm re-reading "Test-Driven Development by Example" (http://www.amazon.com/exec/obidos/tg/detail/-/0321146530/qid=3D1118722781/= sr=3D8-1/ref=3Dpd_csp_1/104-5276191-3223133?v=3Dglance&s=3Dbooks&n=3D507846= ) and using a suggestion on page 148 that I'm finding pretty useful. I thought I'd share it with the group. The suggestion is to end every programming session by leaving your last test broken. This way, when you sit back down to code again you have a specific place to start. You jump straight back into the train of thought you had when you stopped programming last. I've found technique to be a very useful way to keep my train of thought straight from one day to the next. Funny thing is that I'm actually writing this email because I forgot to leave a test broken the last time I was at the computer. I didn't know where to start, so I ended up writing this email. Pretty silly side-track... Have fun. Ali |