Live data from Hacker News

Ask HN: Are most of us developers lying about how much work we do?

news.ycombinator.com

81–90 of 1001 posts

Re: Ask HN: Are most of us developers lying about how much work we do?

#81
Huh, no, I actually work. I mean, I spend some time reading HN or other research/skill-building (job-related), or on facebook (not job-related) like anyone else. And of course, as you mention, plenty of job related but non-coding time. I consider "talking a walk to think through this problem" working. And nobody can be 100% productive; and I do things like non-work phone calls on work hours when convenient.

But, no, I don't spend days in which I spend no time on my job (maybe an occasional day in which I'm in bad physical or emotional health and can't get it together to get any work done, but don't take leave; these are not typical). Overall, most days, I'm mostly working.

I think I'd actually go crazy if I was in your situation, I don't think it would make me happy, it would make me feel useless and unfulfilled. i've been in situations like that at non-coding jobs, and while in theory getting paid not to work sounded great to me, in fact it was not good for my mental/emotional health to be sitting around all day not working and not doing much else.

Unless I was remote maybe, perhaps I'd just do other things that I wanted to do that really had nothing to do with work (learn a musical instrument, learn a foreign language, make art), and feel fulfilled, as long as I wasn't guilty about ripping off my employer (which I guess could depend on the employer).

You say you weren't remote before pandemic. I'm curious what you did with all that time you aren't working? and how you think it makes you feel to be in this situation, are you happy with it, does it make you feel crappy even though you think you oughta be happy with it, other?

I am also curious what you think of the work you hypothetically could be doing. Is it horribly boring? Does it seem really useless, like nobody is going to care or benefit even if you did it? Are there barriers in the organization such that you don't think you could produce anything that really benefited anyone even if you tried?

I think maybe part of it is that programmers might be wildly variant in productivity? If you're getting good perf reviews, could there be someone else working more of their full time, but producing no more than you? I think maybe at a lot of places, the people doing evaluation simply have no ability to evaluate engineers, they have no idea.

I have worked before with people who produced literally nothing. If they got good perf reviews, I guess it's because their supervisors didn't expect anything? Perhaps their supervisors weren't working much either? Or just didn't know how emotionally to deal with a bad review? I had one coworker who (many years pre-pandemic) "worked from home", but when a rare urgent thing in their domain happened to come up, it turned out they didn't actually have the tools to work on it at home; I suspect they were never working at all from home. I wasn't very happy with this overall condition, but I'd never try to "turn them in" -- not necessarily that it would be "too awkward", but, I'm no snitch and don't want to be one. Who knows what's going on in that person's life.

I would have appreciated a coworker who could carry the load instead, but I've realized that I am significantly motivated by doing a good job, making high-quality products... and many people, and many whole organizations just aren't, they have other motivations. I've learned I'm not going to be happy unless I'm at a place where doing quality work is a motivation of many people.

Also... I actually enjoy writing code?

Re: Ask HN: Are most of us developers lying about how much work we do?

#82
I think we should rather talk about the (history) of working the typical 8 hours a day, which doesn't make much sense for software people if you ask me. IIRC the concept of working 8 hours is more than 100 years old and was considered an optimal value to minimize the number of work accidents and burnouts (for factory workers) and allow for three shifts per day. Hence, 8 hours was (is?) considered to give optimal efficiency for any worker.

For me on the other hand, I cannot do any deep work for more than 3-4 hours during a normal day. However, to comply to the historic 8 hours work day, the rest of the day gets filled with __other__ stuff, which may or may not is reasonable.

As others have mentioned already, I think it totally depends on company size, culture and people if you are able to gaze through a day by doing only a few hours at any given day. This completely coincides with my experience as well.

Re: Ask HN: Are most of us developers lying about how much work we do?

#83
Failing to pass most tech screens is normal, but not working at work is not. I've heard of this kind of behavior before, but my coworkers and I work most of the day, with a few breaks, and sometimes stay late if we're really engaged in a problem. I'm not terribly surprised you can get away with it, but self-discipline is a critical part of your character and well-being, so don't lose it.

Re: Ask HN: Are most of us developers lying about how much work we do?

#84
Please indulge my curiosity.

This might be wildly unrelated but... how attractive are you, physically? Are you thin? Are you taller than most people in your peer group?

Do you more or less resemble the "dominant" demographic where you live? That is, the same gender presentation, ethnicity, etc. as most of your government and business leaders.

Are you a citizen of the country where you live?

Re: Ask HN: Are most of us developers lying about how much work we do?

#85
Seems like there are multiple issues here. The first would be rather ineffective management that fails to notice or address a lack of productivity. The second would be a lack of interest in one's current role - most folks would probably do more work if only to alleviate day-to-day boredom, especially given the aptitude that the OP clearly possesses.

I worked at a company where someone like this was eventually unearthed, and the result was all manner of big-brother-esque counts of commits, etc.

Is the argument about morality or managerial structure?

Re: Ask HN: Are most of us developers lying about how much work we do?

#86
post #75
post #55

> Do people regularly run into coworkers like me during their career and simply ignore it because they find it too awkward to criticize them? Yes exactly this, especially at larger companies. I know a few of those developers, and they sit right near me... They find a way to make any task take forever... If it was a smaller company they would be called out, but at my [very, very] large company - its very hard to get f…

Large companies have a tendency to throw up all sorts of impediments to actually getting shit done. Simple tasks can take 3 weeks because there are 7-9 dependencies throwing sand in the gears. This not only provides plenty of cover for not getting stuff done it also saps the motivation to get it done quickly. Like, if X team sits on your request for a week that prevents Y feature from getting out are you really gonna…

Wow. A mere 3 weeks to get something done.

I worked somewhere once where it took 8 months to implement a two page sign-up process, and I counted about 60 people involved. A colleague said I didn't know the half of it and that there were actually more than 100 people involved.

I didn't last very long.

Re: Ask HN: Are most of us developers lying about how much work we do?

#87
If you're in places where you're getting away with this, the likelihood is everyone knows but doesn't say anything because they're doing something similar. Including your managers.

Most businesses just don't need all their employees running at full capacity. I've been professionally programming for nearly 30 years and I've seen this be true in small businesses with The weird thing is you can often get yourself into trouble if you get too ambitious in such situations. People don't want their comfy little boats rocked too much.

From my experience the places that require running on all cylinders all the time are either incompetently managed (which includes understaffing) or very ambitious. Or both I suppose. The thing is, real ambition is much rarer than you'd think given how much society claims to value it.

I've had times when I was happy at both ends of the scale. Cruising is comfortable. Ambition is exciting. Both work for me at different times, but I do eventually tire of too much of either.

I will say ambition and full-speed-ahead only works for me when the goal is something that has value to me. Either a big financial reward or I believe in what we're building. I'm not going to do it as a cog writing your accounting software package.

Re: Ask HN: Are most of us developers lying about how much work we do?

#88
This is not uncommon. I know developers who pace themselves, either by doing less than they are actually capable, or alternatively, simply get more work done than they talk about in their standup and save it up, so there is something to talk about the next day, etc.

It doesn't help that many of the folks involved (scrum masters, PMs) are utterly clueless. If you have a particularly weak team, you may not even need to pace yourself... just do whatever.

Re: Ask HN: Are most of us developers lying about how much work we do?

#89

I have never done what you describe, except perhaps in times of illness when it was understood that working less was a reasonable accommodation (in that particular case, I had leftover brain fog from general anesthesia). I've never heard of any colleagues doing it either. I would never snitch if it happened, but I would certainly consider that person untrustworthy or think that they have an undisclosed condition that…

Most of the other answers focus on how programming is not typing (which I agree with, of course), but I think they miss the point. Yours answers directly and I agree with it.

Working 5 to 10 hours a week seems very low to me, though as a lead or as a coworker I would judge OP by the impact, not by the time spent behind the computer. But I doubt anyone can have serious impact in such time.

I had the chance to work with a brilliant coworker who preferred to slack off - and have passed on recommending him for this very reason.

World is a big place and there are many ways to go through life, so I'm not judging - but if you're asking if this is common, then the answer is "no, not at the places where I worked, and not how I work".

Of course you would have to pay/promise me fortune to get more than 40hr weeks from me, but I'm not hiding that. :-)

Re: Ask HN: Are most of us developers lying about how much work we do?

#90
I don't know about "most of us", but certainely not all of us. I work a solid 7h a weekday (not all of which is at 100% productivity, but all of which is work), and I know for a fact my colleagues work at least as much as I do (I personally think most of them work too much).

And I seriously doubt you'd be able to reach anywhere near an acceptable output working Personally, it makes me uncomfortable to think that there might be so many other people with this mindset around, lying to coworkers and doing the absolute minimum to get by. In my current role, I feel passionate about what we're building and being a startup, we need to maximise efficiency: I'd have zero remorse flagging that somebody is doing close to nothing when everybody else is so involved and relying on each other to do their job. In a corporate environment, I suppose I'd either join you or quit out of lack of respect for coworkers and company.

Post reply on HN