You’re in front of your favorite 24” monitor or your nicer 10” netbook, programming (code & test, code & test,…), writing your code and unit testing… do you get the same feeling I have (actually I had)? I mean: “Just a few lines of code and I’m done. I can see this thing working and move to the next thing… almost there, almost done…”
The adrenaline is kicking in and you’re programming very fast to see something happening, something like: it compiles, green bar on unit testing, click the button, I see the results, done!
You stay there on that chair until you see that thing working and then… next one… and start again.
Well I’ve realized that this is the coffee programming: intensive, fast and furious I’d say. You just want to see your stuff working and don’t want any distraction… no pauses, no interrupts… just coffee!
But what I’ve seen during my programming days was that actually I needed a different approach: the chamomile programming.
“What’s that? Do you really mean drinking chamomile during programming? Are you crazy?”
Just a second and I explain my point of view.
Chamomile programming is the only way I’ve found to rest a little bit from the intensive pace of writing code and testing.
It’s the way I like to write code: calm, with a sustainable pace, taking time to understand the pros and cons of that technical choice, design or architecture, looking my code from a different perspective and sometime going back and re-write it.
It’s the approach that worked many times for me to find the right tradeoff between creating nice code and releasing the product to my customers.
I need time to rest and look back, I need time to understand what I’m doing and drinking a good cup of chamomile (light tea, tisana or light cold tea in the summer) is a nice way to do it.
Drinking coffee (I’m italian so you may know how much caffeine it means… 5-6 expressos in a day are really counterproductive) is not my way: working too fast is not my way.
It’s all connected to the application of refactoring: code & test all the time means refactoring all the time… there’s no other way to coding in my opinion. But to refactor your code you need time and clear vision: coffee didn’t help me, chamomile yes.
And you? Are you a chamomile or a coffee programmer?