Live data from Hacker News

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

news.ycombinator.com

41–50 of 1001 posts

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

#41
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 is between them and HR.

As you covered in your post, we don't write code 8 hours a day. This is normal. Meetings, context switch and times when focus is unachievable are expected and mostly understood by my experienced management. So are times when we are monitoring technology advancement and keeping an eye on the industry and community (e.g. lurking at HN but not overly posting and commenting) and times of social activity between workers (e.g. talking about the weekend).

Most of us take mental health breaks between meetings and need to take time to think through issues. Many also need to periodically break focus to think about personal life issues or hobbies. As long as you generally strive to work, this is not a problem either.

But walking into a stand-up and then lying about your day? To me, that's unethical.

The real question to me is:

Do you do that on purpose or is this something that happens even if you are trying to focus? There are many conditions, from stress and anxiety to diagnosed mental health issues that can prevent you from focusing. Burn-outs and bore-outs also come to mind.

In my eyes, the fact that you asked the community about it shows that you have some form of concern towards that behavior. Would you say it is negatively impacting your life?

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

#43

For me, I find there are peaks and valleys - there are times when I'm so overwhelmed with coding tasks I feel like I'm drowning and other times when there's a lot to do, but all of it's blocked waiting for somebody else to make a decision/finish doing something/approve a budget/etc. When I first found myself in the "wait" state, I figured the logical thing to do would be to proactively find something to improve: docu…

I’ve been in the industry for over a decade at this point and I’ve found when I’m in the “wait” state, I just do whatever I want. If it works out, I show people and so far it’s always gone over well. If it doesn’t turn out, I don’t show anyone, and nobody seems to get excitable about what I’m doing.

I’m in that state right now, so I’m making an elastic search database and flapping grafana on top of it to injest and visualize all our logs. It’s been a pain point for a long time so I think it’ll go over well. I’m also compiling a c++ qt app to emscripten so we can host the app and connect with a smartphone instead of lugging a tablet around.

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

#44
I think you're definitely an outlier, taking what you say at face value. My unsolicited advice: stay abreast of where software is going. What you're doing may make you vulnerable to obsolescence if you're not careful, and you'll only have yourself to blame. Also, I wonder about the health of the companies you work for, ceteris paribus.

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

#45
For me personally, I am going through this for the past month, however its because for the 5 months before I was working basically 50-60 hour weeks with tons of active debugging, coding, and triaging (HW bringup type work). But next month we start ramping up to start new projects.

It could just be what you are doing isn't fundamentally that difficult and doesn't require a 40 hour work week and there is absolutely nothing wrong with that. If people think you're worth the money you are getting paid, then you are worth that money. They pay you to get things done, not to sit in a desk for 40 hours a week or be stressed for performance reasons.

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

#46
post #4

i monitor my work using a plugin and usually get 2-5 hours of code a day... and i have to do all kinds of communication work as well (JIRA, investigation, prepping QA test cases, documenting PRs) i looked back and was getting 1k lines merged every 2 weeks on average. nothing crazy I know but theres much more then just coding to my job, thats just reality. Days/weeks where i dont get a certain amount of code done i fe…

1k lines per week sounds like quite a lot. I'm a dev whose role is mainly supporting legacy systems and sometimes I write probably ~50 lines in a week and feel incredibly productive due to the issues I've resolved.

to clarify, my post says 1k every 2 weeks, not per week.

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

#47
you're not alone. I probably work the same amount as you. I ship stuff the org feels customers love, I get promotions, and get paid well. I could grind so much more but I like to spend my day in other ways. I like to read the news in the morning, clock out at 5 etc.

We have the ability to "work" this little and still be valuable because writing code has a very high barrier to entry. That 5-10 hrs of work took years of learning.

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

#49
I got a bad rating this year for being slow. We have about an average of 4 hours of meetings everyday. I'm not sure when they want us to get work done. I'm tired of working hard and not it not paying off. I work, but don't go too fast.

So I have been called out and punished for it.

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

#50

I think there's also something to be said for passive processing. Sometimes I'll know I need to write some code or some function and I'll just think about it in the back of my head while doing other things, sometimes for a whole day or two. Then I'll sit down and write it in like 20-30 minutes. Did I work 20-30 minutes, or have I been working for a day or two? I would say a day or two, and the 20-30 minutes was the t…

> Did I work 20-30 minutes, or have I been working for a day or two? I would say a day or two, and the 20-30 minutes was the time needed to produce the deliverable of that work.

I would say that I do this too. There's a lot of stuff I can more or less do on autopilot and stuff that requires actual attention and finesse, for lack of a better word. I feel like management thinks that I'm good at my job for all of the autopilot stuff that I can crank out, and that makes up for the time I spend implementing one of the more interesting bits.

I think one of the ways that remote work changes this is that I can do other things while I think through a tricky problem; I can do dishes or walk my dog or something instead of trying to look busy in a room with 6-12 other people who are furiously typing because that's how the manager and project manager understand that work gets done.

Post reply on HN