If you’ve used Git before, the concept will be familiar.
More tools than I’ll be able to fit into a blog post, even a long one, but the documentation is detailed and up-to-date. (You may be aware of my love of plain text…) It does some automatic time tracking, has a variety of tools for viewing your entries, and includes a few ways to do things like filtering, flagging, or archiving them. The command updates a simple TaskPaper-formatted text file. It does this using a terminal command with an intuitive syntax. The basic idea of doing is to provide a way to keep track of the little things I work on over the course of a day, both as a reminder after I leave and forget what I was working on, and as a way to track my productivity. The LaunchBar action is included below, if you’re interested. I have, however, integrated it with LaunchBar and other systems over the years. doing is primarily designed for use from the command line in your terminal of choice. If you’re already sold - or at least enough to skip the spiel - and want to skip right to the documentation and the latest version, just head straight to the doing project page.īefore we go much further, I should make something clear. This is going to be a longish post where I get to talk giddily about all the cool stuff this little tool can do. I find it a very useful tool, though, as long as I don’t think too much about how much time I’ve put into it.Īfter publishing a few new versions over the last couple of months, I thought it might be time to remind potential users (people who read this blog and enjoy my brand of madness) that it exists. Given I’ve been working on this as needed for 5 years now, it hasn’t felt like a descent into madness as much as a gentle slide into areas of questionable judgment. You know how git log can be really useful after a long night of hacking, or a few days of being away? 1 This is that, but for everything else, and it’s brimming with handy features. It not only creates rich logs of my time at my computer, it also handles time tracking and reporting and integrates with my system via LaunchBar, various automations, and GeekTool.
I haven’t written much about doing since then, but I continue to use it daily.
GEEKTOOL 2020 SERIES
The journey was well documented up to that point in a series called, appropriately enough, “Scatterbrained.” By 2014 I’d come up with a solution in the form of a command line utility called doing. After VoodooPad, I had a system going using QuickQuestion and nvALT.
It was partly for record keeping, but mostly to be able to walk away from my computer and still be able to remember what I was doing when I got back. Back in 2011 I started tracking the minutiae of my work days using VoodooPad.
0 kommentar(er)
