4 ms·

I think you're completely right, however I'd love to see a graph of average work time claims on HN plotted against this. There's no denying that there are far

I think you're completely right, however I'd love to see a graph of average work time claims on HN plotted against this. There's no denying that there are far more people claiming they work 60-80 hour weeks than would collate with the data that you and OP have provided. I think these people are generally overworked but are also poor assessors of their own performance, taking worst cases as averages and calling a day in which you finish at 5pm but answer a slack message at 9pm, a 12 hour day. Not to be too sardonic, but: I'm on call frequently but I don't tell people I've been working for 24 hours because I got a page at midnight, even if it can feel a bit like that by the end of the next day.

tardigr8 5y ago
We tracked work hours using a custom desktop app in our team (made by the team over several iterations to make it not burdensome), and insisted that devs log time against the downtime category (only during work hours of course). Some of the more senior devs were very honest about their downtime. Some days they would log 4 out of 8 hours downtime. Usually after a strenuous week or late night deploy. Examples of this are shooting the breeze for an hour, going on a wiki binge etc.. We were all surprised by the actual numbers coming through and the numbers in the various categories. Emails and project admin would average 20% of total team time. “Firefighting” which was attending to unscheduled troubleshooting was 15%. If you don’t believe someone who says they work X hours per week, you are probably right. We found there is a lot of minutiae, and a lot of down time when tired. Which we didn’t realize until we spent the time to log it. If you do work long hours, I can heartily recommend implementing an easy time tracking system for yourself with categories. From our experience, it reduced the hours you worked, forced you to get some sleep and exercise, and made you more productive in the hours you do work.

tardigr8 5y ago

We tracked work hours using a custom desktop app in our team (made by the team over several iterations to make it not burdensome), and insisted that devs log time against the downtime category (only during work hours of course). Some of the more senior devs were very honest about their downtime. Some days they would log 4 out of 8 hours downtime. Usually after a strenuous week or late night deploy. Examples of this are shooting the breeze for an hour, going on a wiki binge etc.. We were all surprised by the actual numbers coming through and the numbers in the various categories. Emails and project admin would average 20% of total team time. “Firefighting” which was attending to unscheduled troubleshooting was 15%. If you don’t believe someone who says they work X hours per week, you are probably right. We found there is a lot of minutiae, and a lot of down time when tired. Which we didn’t realize until we spent the time to log it. If you do work long hours, I can heartily recommend implementing an easy time tracking system for yourself with categories. From our experience, it reduced the hours you worked, forced you to get some sleep and exercise, and made you more productive in the hours you do work.