Ask HN: Do you log your time at work?
Some colleagues log time at a macro level: at the end of the day they enter what they did, based on what they remember. I believe this way of logging is not precise enough though because you can easily overlook time you spent on some tasks. For example I do a lot of reviews: there is no way I can remember at the end of the day how long I spent reviewing each pull request. So I track my time as I go, using Toggl. At the end of the day I sum up time spent on all tasks and enter them in JIRA. That's annoying to do, as I end up logging time slices of 20, 10 or even 5mn (some reviews take short amount of times, others requires more).
Do you log time at work? If you do, do you do it at a macro level or do you try to be more precise? Do you use any tool to help you?
25 comments
[ 3.2 ms ] story [ 58.0 ms ] threadYou have to ask yourself, what value would you get from estimating that a code review will take 10, 20 minutes? Is that kind of information particularly useful for forecasting? I would guess it isn't because it seems too granular. Nobody I know sits down and plans a series or 10 or 20 minute code review sessions. They usually plan out bigger blocks of work.
I use a tool called Track - Simple Time Tracking and Invoicing (https://itunes.apple.com/us/app/track-simple-time-tracking/i...)
Full disclosure, I built Track and I own the company that sells it.
I built Track because I wanted a cleanly designed time tracking tool that syncs my data between devices and doesn't make me sign up for an account. It's iOS-only. It works on the iPhone and iPad.
So yeah, I use the tool that I built. I use it every day while I'm working on my client projects.
You set up some tags and tap on them to start the timer. For example I track things like meeting times or time spent in code review. Also generates reports and gives you JSON to write custom apps with.
By the way, I don't have any affiliation with the app or company, I just think it's a well designed app
I've been a paying customer for over 5years, and well worth EVERY penny!
Example: (/Todo-New taks name here –Project project name –Due 1/1/2016 –Tags #one #two #Three –Time 2h)
Anyways, I do track time because we bill hourly and eventually I have to move the totals for billable work from my app into our timesheet system (very clunky Microsoft Project Server).
I use Freshbooks for invoicing, and it also allows simple time tracking, for which I use a macOS dashboard widget (a bit outdated, but it works).
In my experience, the requirement for per-task time allocation is not met with the appropriate review and tally at the PMO level.
It is more pain than gain.
Disclosure: I'm the author.
Only thing I am proud of in that project is the firebase support. Since I was managing my tasks on 2-3 computers, I had to build something that syncs itself. I am thinking of packaging this thing, so that other people can use it in thier command line.
[0]:https://github.com/FalloutX/cmd-todo
Note: the mobile interface is very dated. I only use it in desktop.
https://github.com/angusfretwell/jiggl/blob/master/README.md
If I don't have enough tasks/hours allocated, I look back at anything I did during the week that isn't on the allocated list, and I have it added to the allocated list and then I write the hours in. Sometimes, I'll do this during the week rather than all on Friday.
The purpose is to fill in the boxes and make the numbers match. Nobody ever examines the boxes and numbers, and they bear no relationship to what actually happens. If I don't fill in the boxes and make the numbers match, someone comes to insist that I fill in the boxes and make the numbers match.
In the ones that I get added, I pick the number. Other ones just appear with numbers already in them. Sometimes I like to spread the numbers out. Sometimes I just do them in big blocks.