5 ms·

Very cool! I wrote a project a few years ago to do something similar: https://github.com/christiangenco/t_time_tracker https://github.com/christiangenco/t_time_

Very cool! I wrote a project a few years ago to do something similar: https://github.com/christiangenco/t_time_tracker https://github.com/christiangenco/t_time_tracker It lets you add tasks like this: $ t browsing HN Started: browsing HN (now) $ t @website writing blog post Finished: browsing HN (0:12) Started: @website writing blog post (now)

ttscoff 13y ago
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/ 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`
ttscoff 13y ago
By the way, I've always thought ActoTracker had potential but I haven't locked into it yet: http://freecode.com/projects/actotracker http://freecode.com/projects/actotracker
bcornelissen 13y ago
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.
- christiangenco 13y ago
  Pull requests are welcome :)
  - bcornelissen 13y ago
    I don't have particularly awesome coding skills but I'll see if I can find the problem and come up with a solution ;)

ttscoff 13y ago

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/ 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`

ttscoff 13y ago

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

bcornelissen 13y ago

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.

christiangenco 13y ago
Pull requests are welcome :)
- bcornelissen 13y ago
  I don't have particularly awesome coding skills but I'll see if I can find the problem and come up with a solution ;)