|
|
|
|
|
by dreeves
5028 days ago
|
|
Ah, the idea of TagTime is to be a happy medium between something like RescueTime (where it automatically infers where your time goes based on what app or web page is in the foreground) and manual logging where you explicitly clock in and out of projects to get your exact time spent. Details are in this article: http://messymatters.com/tagtime Short version: TagTime randomly samples you with a popup, asking what you're doing right at that moment. You never have to remember to do anything, so it's essentially passive. But you're not trusting the computer to infer what you're doing, so it's perfectly accurate (asymptotically -- you need a week or so of data for the inherent noisiness to average out, ie, to get a big enough sample size). |
|
Part of my suggestion, left unspoken above, is that once a day or once a week, the person would "review" the screen shots. During this review, the same (time-stamp, tag) pairs would be (manually) created that are created by your pop-ups. Its just that the "pairs" (or records) would be created in batches, rather than at the time of the events they refer to.
Now that I am done trying to head off a possible misconception, let me say that I plan to try your way, because there is already software available to support it. (I have software to automatically create the screen shots, but not software to support the task of reviewing the screen shots while manually creating the (time-stamp, tag) pairs.)