38 A Flow

Courtesy to Wikimedia Commons under CC

Yesterday I really got started doing work after my contribution to this project. Somehow it was amazing. After hitting the Publish button, I had this strong feeling of accomplishment. And that feeling helped me getting started with my day job work.

I took my task list and scanned it for the one most important thing to do. Since I had a database development packages with a due date of that day, I picked that on. But that was one entry on my list. How to tackle that block, big enough to keep me busy for a day? I broke it down into subtasks and about 15 minutes later I was ready to start.

Granted, I had a good run then. Maybe I also would have without subtasks and stuff. But with the broke down list, I already had structure. I started with the first item, it was weeding out old and no longer needed code fragments. I committed versions to my local repository along the way and then was ready to tick off the first subpoint. A push to my online repository later, I was into the next subtask.

By noon I had ticked off all the subtasks but the final test. That would be a calculation on the database that should be reasonable fast then. I started it and went to lunch with my coworkers. After returning to my desk some 45 minutes later, I discovered it took only about two minutes for the calculation. Compared to the two hours before a great success.

I closed my “Most important task” and did another half hour of emails, planning and cleaning up. After that, I was free for the rest of the day. I not only accomplished more in four hours than normally in a workday but also put the project back on the timeline.