That is a seriously good idea, love it.

I made doing because I get manic and don't even realize I'm switching to a new task until I've already forgotten what I was doing before. It's probably not an issue for most people. So, for me, I have Day One pop up every hour and ask me what I'm doing, which then gets converted to a "WWID" file in nvALT via the library in doing (and Hazel). If I do remember to track between tasks, I just jot it off on the command line.

I love the idea of a timer, though. I do use Timing to do something similar. http://timingapp.com/

And the organization by nested CSVs has some great potential for longer-term data collection.

`doing now writing too long of a post on HN`

I tried your project and found a bug. When a task starts on one day, and finishes on the next, the total time reported is negative.

for instance:

  23:34, task started
  00:09, task done
  expected time spent: 35 mins
  reported time spent: -24 mins

Aside from this bug, I really like it and plan on using it.

Pull requests are welcome :)

I don't have particularly awesome coding skills but I'll see if I can find the problem and come up with a solution ;)

By the way, I've always thought ActoTracker had potential but I haven't locked into it yet: http://freecode.com/projects/actotracker