Ask HN: How many of you have to log hours?
Hi
I am a programmer and in my job I need to log all my hours against tasks in Jira, and submit that did the 40h.
Sometimes I don't like it because something takes longer than it should then I get pulled up on it. Sometimes the reason is I had a bad day couldn't concentrate etc. But it isn't good to say that so I need to invent an excuse.
My last job was similar and I really dislike it because it can only be bad for the programmer. Especially given how hard it is to estimate stuff.
Btw this is product dev work not billed out to client work. Those jobs I purposely avoid.
(
21 comments
| 12 points
| on HN
)
So I made a read-only log, shared it with them, and started writing down everything I was doing to make their products. It ended up being really interesting as I never really analysed my development process, all the false tracks you go down for a while before reverting, all the data format changes, type errors you meet, avoiding repetition, documentation, flashes of inspiration, or how waiting for a query to complete breaks your flow... and I think they got a better idea of what is involved in producing stuff (no, it's not "just updating a few graphs" if you went and changed all the definitions and they come from 7 distinct data sources).
A side effect is that they got precisely the hours they paid for.
With other clients, I routinely used to put in a weekend or late nights if things didn't quite work, or if I had an idea for an interesting product that could be helpful to them. With these guys, it was "this is probably going to take me 10 hours. Can you approve these hours?" and 2 weeks later they'd say "OK" and I'd get started only then. They were so hours-driven that when I passed them a new product I did do in my spare time, they refused to even have a meeting to look at it in fear of having to pay for more hours. Quite amazing.
So people who can't automate feel cheated by people who can.
The best projects I've worked on had:
* A manager who was technically literate.
* The tasks were documented and specified clearly.
* The project plan was prepared by a knowledgeable planner and thus realistic.
* Our weekly progress meeting focused on addressing the delay causing stumbling blocks.
My days as an employee are over. As a consultant, I bill for the completion of specific deliverables. I simply decline business from potential clients who demand an hourly rate. I just can't be bothered doing time-sheets and justifying why something took more time than planned. Occasionally I do underestimate the amount of effort a deliverable requires. That's the cost of doing business on my terms.
And the government. We recently started selling to the government, and now we have to report our tasks and hours. Every two weeks has to have at least 80 explainable hours.
Considering the audience for HN has not only developers, etc. but also management/entrepreneurs, it would be handy for lists like this to be compiled from Ask HN comments so that they could reference it and try to be better managers.
What I learned from this experience: the data either was not used or nothing noticeable changed because of it, it made people angry, it wasn't even close to accurate. Now it's one of the questions I'd ask at the interview (red flags: task time tracking, no source control, no testing, no qa plan, too many managers per project, tech choices are political not from engineering, ...)
If you're new to using emacs, just use it for everything, every day, every time and after 3 months you'll be comfortable with it and might be able to like org-mode.
There are lot of resources over the internet, stackoverflow, mailing list, blogs, etc. If you're keen to learning emacs then the most important thing is just use it, use it, use it, use it.
[0] - http://doc.norang.ca/org-mode.html#Clocking
[1] - http://doc.norang.ca/org-mode.html#TimeReportingAndTracking
Likely, however, they are not really going to say anything. Some managers are old school and simply feel collecting time on everything is the way it's done, but end up doing nothing with the data because they're lazy.
[0] On the subject of reviews. If you ever walk into a review and have no idea what is going to be on the review, your manager is doing everything wrong! Leave that job as soon as you possibly can. Period.
I worked at a place where the management tried to implement something similar. All of the main engineers left within about 2 months. They missed their big deadlines and over the next 1.5-2 years the rest of them (including management) lost their jobs. The product was sent off-shore and kept of life support for the remaining SaaS contracts. It was really quite sad to see something cash flow positive sink right to the bottom over something like that.
I will only got better at predicting time, when log/report ing real-hours not expected-hours.
I also set a maximum time spent blocked on tasks, ideally a short period, and reported every time I go beyond that point. This way if I needed help, I could get it. If help is not provided, employers wont be surprised by work schedule.
Our minimum unit of trackable time is 30 minutes. This helps us recognize how expensive context switching is.
Most importantly, each member of the team is only allocated ~30 hours per week to allow for all the nonsense that has a tendency to pop up.
It takes time to do programming work. Sometimes you need a good think. Sometimes meetings distract you. And even off hours, I'm often thinking about how to do stuff. A problem at work, I might set aside, have a good night, and wake up in the morning with a solution.
Anyway this sounds like poor management. I don't have a really great answer on that.
For the benifit of being able to do accurate estimation comparisons, retrospectives, hunt time vampires etc - I personally think it's worth it.
it does not bother me, in fact sometimes it helps me realize I might be getting burnt, when i see the numbers go too far up, I see it as a barometer.