by acalderaro on 4/10/17, 9:11 PM with 155 comments
by throw832649 on 4/10/17, 10:16 PM
I seem to get as much done as other people (sometimes better) so part of me wonders if I'm not as unusual as I feel. Part of me wonders if I should get evaluated for ADHD, since I find it such a struggle to focus on my work. And part of me is just frustrated with myself, that theoretically I could spend like 3 good hours at work each day, get more done, and have more quality time to myself.
by hardworkerthrow on 4/10/17, 11:17 PM
I have never met a single software developer who, when pressed to give an honest assessment and when "working" is defined along the lines of "actively defining, coding, or debugging a feature", self-identifies as working more than 50% of the time. There are occasional stretches of 12+ hour working sessions, but they are very rare.
I'd say I've asked this of over a hundred people.
This isn't to say these people only do 4 hours of work a day. Often, peers have described how they hit a wall at work, go home, and then work on personal projects in the evening.
I've come to the conclusion that is generally impossible to do mentally intensive tasks for more than 4 continuous hours over the long term.
by decasia on 4/10/17, 10:37 PM
"Working" is an ambiguous category, it seems to me. One definition of work (call it "productivist") says that we're only working when we're literally producing something valuable. A more organizational view might hold that "work" is whatever you're socially (often implicitly) required to do to keep your job (whether measurably productive or not). And a third more holistic definition would include stuff like exercise or professional development that are not always directly "required" by anyone, but that you might go crazy without doing...
by lazythrowawayd on 4/10/17, 10:51 PM
Why is this?
I've had a few promising projects languish because my manager is slow or hesitant to allocate resources. That's a bit demoralizing. When I'm on a path to production for a functioning system I get caught up in the devops meeting vortex. That's a waste of time and it takes several weeks to get any sort of resolution. In these cases my time is mostly spent looking for workarounds and not "working". I feel there are a lot of politics and favoritism in the company, and my manager (and our team) is not on the right side. It's demotivating to have your work ignored because you're not a priority. I don't know how anyone stays for more than a year.
Edit: In the first few months I worked on random on-going projects, but was quickly made lead on some new projects. It was good at first, but after about 9 months I'd say most (90%) weeks I don't put in anywhere near 40 hours of work.
The sad thing is I've always gotten a raise (double digit in two cases) and full bonus every performance cycle.
I've finally started looking for another job.
Does anyone have recommendations? I'm really looking for a company that enables their individual contributors (engineers) to actually get shit done.
by ThrustVectoring on 4/10/17, 11:14 PM
by 9erdelta on 4/10/17, 10:14 PM
by superasn on 4/11/17, 6:31 AM
Also each lap is dedicated to one activity, first is manufacturing where I work on my project (the actual coding part), second is traffic (this is the dreaded marketing/outreach part) and finally is the optimization part (seo, increasing conversion rates, improving design, etc).
I've seen that the diversity of this work prevents you from getting bored and also is very good for your sites because if you keep working on just coding your sites seldom make any money.
The 3 hours limit is because after that i can happily watch tv, spend time with my family or just work on my other hobbies besides computers guilt free.
P.s. When you try to do as much work as you can, i believe you still only get 3 hours of work done - yet you feel guilty of not doing enough which causes unhappiness.
by throw112358 on 4/11/17, 12:05 AM
by webjac on 4/11/17, 4:29 PM
I never worked more than 4 hours (of real work a day). There's the occasional super productive day where I have done over 8 hours of productive work, but that's the exception, not the rule.
I usually work around 3-4 hours of productive work daily. Heck I'd even say 20%-30% of that time is not even productive (meetings, emails and necessary yet unproductive things).
When I worked for companies doing 9 to 5, I wasted a looot of time doing nothing: reddit, fb, and stuff. I also recognize that I need that distraction to do some real productive work.
I'm very fast and productive when it comes to actual work, but if I don't get the procrastination time then I just become a blurry mess of a brain and take 10 times longer to do the same things.
by swah on 4/10/17, 11:38 PM
But there are SOME DAYS that I work 150%! ("in the flow")
So how to achieve flow consistently?
One of the few things that works for me is to get started working first thing in the morning: no news, no HN, until 10am, etc. When I can do this, I know I'll have a productive day.
by slizard on 4/10/17, 10:10 PM
by iLoch on 4/10/17, 10:35 PM
by throwaway_jazze on 4/11/17, 5:36 AM
Significantly less now that I work remotely, on my own schedule, and at a reasonable company. I get 6+ hours a day of real work in, usually more, but try not to overdo it. (For awhile I was becoming a bit workaholic without the boundary between work and not-work, spending 10+ hours at it.) I take breaks and do spend a little time on HN or Stack Exchange to clear my head, but I don't do Reddit, webcomics, facebook, or any random sites during work. That's my relax after work stuff, done on a different PC. So in terms of productivity, I'd say around 75-85% work, 15-25% slack most days.
I previously worked an 8:30-5:30 where management measured productivity by the butts-in-seats metric, scheduled a lot of meetings, and was quite anal about punctuality. I was lucky to get 4 hours of serious work in most days (between all the interruptions, bureaucratic stuff, and having to work based on my manager's sleep schedule). Sometimes I ended up doing more work at home at night than I did while 'at work'. Maybe 50% productivity, often less.
Before that I worked at a 9-5 where we had to record our time per task so specifically that we even had a task to enter the time spent filling out the timesheet. I could have done better there about focusing on solving problems and improving business if I wasn't constantly distracted by the clock ticking and all the estimating and meetings about estimates and deadlines and timesheets. Maybe 50% productivity.
by justrudd on 4/10/17, 9:29 PM
Unlike most people, if I finish my work in 5 hours, I go home. If I'm not going to be working, I'd rather not be working at home. I've never had any complaints about work quality or throughput. I have had one complaint about not being seen in the office.
[edit] clarified the 35% bucket
by neal_jones on 4/10/17, 11:04 PM
by mikekchar on 4/11/17, 12:07 AM
For me the answer is "absolutely!!!". Reading through some of the responses, it really seems that people are mixed. Either their "non-working" time is spent with side projects/training or they have become demotivated by problems with the work flow on their team.
For me the latter is by far the biggest problem. I was just thinking the other day that, as programmers, we need a kind of statement that indicates what we expect from the organisations we are in.
To be honest, I really want to work instead of write stuff on HN, so I'll leave this as an exercise to the interested. As an example, I think it is reasonable to expect to be able to spend whole days writing code (which means that someone else has to go to the meetings, and someone else has to clarify requirements, and someone else has to prioritise). There should be some clear resolution of differences of opinion (whether that be in technical direction, or whatever) -- a programmer shouldn't have to spend time arguing. A programmer should expect to have spaces both for interacting with groups of people and for quiet contemplation. I sure there are other (and better) ideas, but that's what I have off the cuff.
by throwaway184827 on 4/11/17, 3:08 AM
(Yes, I know it's wrong and I want to be more productive, but I hate the work I do and I hate the culture here. So I want to start my own thing.)
by dylanha on 4/10/17, 10:26 PM
by throw110 on 4/10/17, 11:38 PM
... so it needs to be done to check an item in a list but nobody cares. If nobody cares, I don't care either, which makes me think I'm wasting my time, which leads to depression, feeling burnt out, procrastinating even more, etc.
by jonahrd on 4/10/17, 10:47 PM
by IAmGraydon on 4/10/17, 11:19 PM
by iamben on 4/11/17, 12:45 AM
That said, if I'm rolling and happy it can be way more, if I'm tired/struggling to hit the flow/not creative - way less. I can get an awful lot done in a day (or few days) if I push, but doing that long term becomes counter productive.
On a regular day, I'll also get a bunch of smaller 'work' done, but it's mostly the admin-y stuff. Sales, email, help, calls, networking. Sometimes that can be my whole day - I suppose it depends how important those things are at the time (sales!) as to how much they're considered 'work'.
Edit: Just to add, decent headphones are a godsend.
by truebosko on 4/11/17, 1:15 AM
Important breaks I do take: Coffee walk (unfortunately on some busy days I simply can't make it out), Quick chats with the team, and Pomodoro-timed walks to stretch/ease the mind.
I usually eat lunch at my desk, which annoys me, because I always want to socialize and be better at that. I don't find it easy to do this since the days are so busy.
I'm a product manager, so I spend much of my days in meetings that are a mix of working sessions, scoping exercises, communications with external clients, and team-focused meetings.
On the days I don't have any meetings (they do exist), I zone out and get some work done. Lately I've been focusing on the DevOps for our team.
by donatj on 4/10/17, 10:09 PM
by ivm on 4/11/17, 1:46 AM
I also spend 1-2 hours a day on my "leisure laptop" (for example reading HN from there but also some useful RSS feeds). So it feels like 65% would be a correct productivity score.
Tracked with https://qotoqot.com/qbserve/ of course, most of the productive time was spent on its development and marketing. :]
by qrybam on 4/10/17, 10:22 PM
Quiet day = maybe half my time
Most of my days are busy; if I'm not busy with my main work then I'll be busy making the more mundane aspects of my job disappear into the background.
edit: formatting
by jpindar on 4/10/17, 10:25 PM
by workthrowaway19 on 4/10/17, 11:13 PM
The bigger we get the more lawyers and compliance people we ad, and the less noticeable it is that I'm not doing shit.
by mdlap on 4/13/17, 11:49 AM
The reality is that 100% of my time, if meetings are included, is productive (excluding minimal breaks).
I feel sorry for the people trying to run businesses with all of these employees not working.
I'm a QA engineer. The most experienced QA engineer on a 3-person team (the other two have either more experience with testing but less with development, or vice-versa). I have waaaaay too much to do to get away with not working.
I do empathise with those for whom maintaining a high level of productivity is impossible because of how demanding their work is. I'm fortunate that I have so many different tasks to perform that if I don't have the energy to concentrate on something demanding, I can switch to something fairly basic.
I'm also fortunate in that, for me, problem solving activities are almost always energising. So if I feel like I'm getting burnt out I can dive into one of the tricky but non-urgent problems I hadn't got around to yet.
by Jemaclus on 4/11/17, 12:44 AM
That said, I don't necessarily care that much about the hours my employees work, so long as they meet the deadlines and are reasonably productive. I have a good idea of how long a task takes, so if they take too much longer than that, we'll have a chat. Otherwise, I just want to make sure they're happy and not burnt out and staying as productive as possible.
by AnimalMuppet on 4/10/17, 9:22 PM
Honestly, my best guess is 50%, or close. I still get my work done as fast as everyone else, though. No complaints on performance reviews.
by mattbgates on 4/11/17, 12:43 AM
While our company goes with the rest of the world, I wish the company would consider 10 hour days 4 days a week, with half the department working in the earlier part of the week, and the other half working the later half of the week instead of all of us working the traditional 8 hour days 5 days a week.
So I make the best of it and enjoy those days where I do mostly nothing the entire time. But I'm never not doing anything.. I build web apps and run a popular website, so I'm always kept busy.
by milkytron on 4/10/17, 10:36 PM
by CGamesPlay on 4/10/17, 10:44 PM
Putting this all together, I spend 37.5 hours / week productively and 12.5 hours / week at work slacking off (or doing human things like eating and pooping). So call it 75% productive time.
I generally enjoy my job. I've counted writing this post / assembling this data as "not productive" time.
by ChuckMcM on 4/10/17, 11:06 PM
One of my 'problems' is that I can't "not work" in the sense of a laborer who is no longer building widgets. As a person who is asked to solve complex problems with a high degree of dimensionality inside of an arbitrarily constrained solution space, much of the 'work' I do consists of turning the problem over and over in my head while I explore the solution space.
A good example of this was an early review I got at Intel by my manager (a really solid EE type guy). He added some criticism of my time management (considered a 'ding' in the vernacular) for a embedded compiler/assembler/driver thing I wrote as part of the evaluation of a graphics processor. He said I had 'sand bagged' the time estimate.
When I asked him to describe that a bit more he explained that I had told him it would take 6 months to do, and it was 2 weeks late, and I had spent 5 months "goofing off and not working" and then about 6 weeks doing the work. So my estimate should really have been '8 weeks' and if I had started on time it would have been done two weeks earlier than that.
I thought about that for a long time. And explained to him the for five months I had no idea what the best way to write the software was, and in that five months I had learned about 8 different technologies that all came together into the final solution. I had to learn how to write device drivers in Xenix, how to map I/O space memory into the kernel, design a language which was human understandable and could be compiled into the odd little RISC instruction set of the Graphics chip. And until I had figured out all of that precursor information, I didn't have a clue how it would be written, but then after figuring out that information actually writing the code was fairly mechanical.
In this one case the problem was that hardware has so many great milestones you can call out, parts captured, schematics done, netlists verified, layout started, design rule verification, first films, films checked, first boards, boards checked, first assembly. Bringup in stages 1, 2, and 3 etc. All along the way there are pleasant milestones to say "this is done" now on to the next thing.
But software is never like that for building something that nobody has ever built before. And it is even rarely like that when you have the same software but you are building it on a different system. The linkages, the entanglement between the system and the software (and now the network and the services) makes each new implementation its own special snowflake, with its own kinds of problems.
Have you ever woken up and "knew" the solution to a tricky software issue? Or had an idea for a change to an existing system that might make it better? That happens to me all the time when I'm designing stuff. And a case could be made that I'm working even when I'm asleep! Not because I'm sitting there typing in lines of code but because I'm going through the solution space, somewhere in my subconscious, looking for clues to places that hold better answers than the answer that is currently checked into the git repository.
As a result I tend to measure my own productivity by 'solutions over unit time' versus 'hours typing into employer owned equipment'. It still bites me from time to time when a supervisor needs a constant stream of 'still flying' type status messages to feel comfortable.
by fatherofone on 4/10/17, 10:47 PM
I watch some videos on latest tech, thats work too....
Only thing that matters is if have I completed tasks in my sprint or are there any critical issues
by hfourm on 4/10/17, 10:58 PM
Rest of time on HN, reading, or admin type stuff (planning, ticket & branch management), and of course meetings
by halis on 4/13/17, 2:55 PM
However, most days, probably 4.5 out of 5 on average, I am super productive, taking very few breaks aside from lunch.
In a typical day I probably get 5-6 hours of solid work done. But there is a downside too.
In order to achieve this, I sometimes skip meetings and ignore requests from other people.
I am considered a high performer and seem to be an anomaly to most people.
by 1_player on 4/10/17, 11:27 PM
by rstuart4133 on 4/11/17, 12:43 AM
If you could that (and I do), I'd say at least 75% of my time is spent working.
by callesgg on 4/10/17, 11:01 PM
I think of stuff that is beneficial to the company in one way or another like 95% of the time.
Re structuring thoughts, digesting ideas.... talking to others to understand how they think.
But if someone that did not know me came and looked at what i did during work hours and did not get to ask questions to me. I would assume they would think that i only worked 20-25% of the time.
Things are not always what they seem.
by nickrivadeneira on 4/10/17, 10:40 PM
by 5_minutes on 4/10/17, 10:12 PM
Working from home is getting things done.
by jarboot on 4/11/17, 1:04 AM
The other 10% is making tea and drinking some, usually looking out the window or chatting with someone.
by nunez on 4/11/17, 2:22 AM
I used to read reddit and hn to saturation on many days before getting into consulting; these days, i hardly read anything until before or after my core hours, not because i can't but because there is more interesting work to do
by MileyCyrax on 4/10/17, 11:22 PM
by ajmurmann on 4/10/17, 11:39 PM
by KerryJones on 4/11/17, 12:10 AM
by glennsantos on 4/10/17, 11:32 PM
Work in my context is time spent on things I planned to do and want to do, including the small breaks I take to recharge and socialize.
by krystiangw on 4/11/17, 6:07 AM
by smilesnd on 4/11/17, 12:36 AM
by brentm on 4/10/17, 10:38 PM
by ubersec on 4/13/17, 2:20 PM
by ivrrimum on 4/10/17, 11:59 PM
So yeah, a hour paid is a hour worked.
by douche on 4/11/17, 12:00 PM
If I work from home: usually 4-6 hours of productive work.
Going to the office adds up to a ten-hour day, with the commute. Working from home is usually a 6-7 hour day, and I get to stay in my pajamas, take the dog for a walk, take a break to do some housework, and be in a comfortable environment.
I don't work from home enough anymore.