I have been experimenting with a couple of methods to find my rhythm in coding and finally I found one that sort of works. Having good rhythm in coding makes getting into the flow state easier and faster.
Here's one I did:
1. Setup a dual monitor environment.
2. Opened my development IDE in one monitor.
3. Opened up YouTube /Google reader in the other monitor.
My rhythm would be:
write a test, fails, make it pass, pop over to YouTube to watch an interesting video clip or read an interesting blogpost for 5 minutes, come back and write a test again.
Works pretty well so far. I manage to prevent myself for dozing off after lunch and my concentration span is longer! Actually it's shorter since I only concentrate when I am writing a test. Definately staying true to one of the core ideas behind TDD; take short, small and simple steps towards your goal :P
I guess I will stuck with this rhythm for awhile and see how it goes :)
update: As I proceed further, I started to realize that when I am watching a YouTube video, I can't wait to get back to my tests again, I guess once you are bitten by the TDD bug, its hard to stop =P
Rhythm in Coding
Tuesday, April 15, 2008
Posted by Thye Yeow, Bok at 2:52 AM
Labels: unit testing
Subscribe to:
Post Comments (Atom)
3 comments:
You better not get caught watching YouTube @ work!!
haha! I finished the whole Initial D fourth stage these 2 days! Need to think of what to watch from tomorrow onwards already hehe :P
wow, if only somebody prescribed this rhythm during my school/college days, I would have been an astronaut by now! damn...
Post a Comment