I fire engineers like you. You're lucky. :)
Ask HN: Are most of us developers lying about how much work we do?
371–380 of 1001 posts
Re: Ask HN: Are most of us developers lying about how much work we do?
#372Earlier quoted context omitted.
Just wanted to point out that this > I truly believed in the mission, worked hard, was paid a lot, achieved great things and was overall very satisfied. and this > used to leave at 5pm sharp are not mutually exclusive. We have this weird thing in tech where we think that, to be passionate, you have to work yourself into the ground. But this is stupid. There's organizational psych research going back decades showing t…
https://pubmed.ncbi.nlm.nih.gov/30793826/ Do you happen to know of good studies to back up --- organizational psych research going back decades showing that teams who work 40-hour weeks will quickly outperform teams working 60 hrs / week --- I've heard this before, but, I've never seen the studies talked about. I found this study via Googling, it took a little longer than I would like to admit. (I'm probably using th…
Results: Working >40 to 50 hours per week and >50 hours per week were significantly positively associated with work productivity in univariate analysis. However, the significant association no longer held after adjusting for work engagement. Work engagement was positively associated with work productivity even after controlling for potential confounders. Working hours were not significantly associated with work productivity among those with high-work engagement or among those with low-work engagement.
Conclusions: Working hours did not have any significant associations with work productivity when taking work engagement into account. Work engagement did not moderate the influence of working hours on work productivity, though it attenuated the relationship between working hours and work productivity.
In my personal experience of workplace since 90's, whenever you have the chance to "level up", work a bit extra to gain a bit more progress and experience, it's absolutely worth it. If you don't gain anything by it or have no meaningful work to do (ie. process-related tasks and projects), it is worth more to you to leave work for another day.
I've become sensitive enough I can feel the stress begin to build at the end of the day, and know which day is worth to leave work (most days), and which rare day is worth more to you to stay a bit longer just to follow that flow out to its end.
Anything new after 3PM can wait to next day. Your mind will anyways work it out in the background if it's important somehow.
Re: Ask HN: Are most of us developers lying about how much work we do?
#373Long time manager here. I call this "work-shy" and it is neither ubiquitous nor rare, I'd guess about 10%-20% of all employees, and it's certainly not unique to software or even to white-collar work. You should think of this as a problem. Even if it's not for your boss or your teammates (and it will be, eventually), it is for you. It is soul-crushing to fill up the hours. Two pieces of advice: 1) The "good" solution…
Or think about why you do the work, what it allows you to do with your life. Doing what you love / loving what you do is one way to be happy, but it isn't a requirement, as long as you have a reason for doing the work. Life is full of things that don't directly bring fulfillment and happiness, such as brushing your teeth, doing the dishes, exercising (for many people), shopping for clothes (ymmv), and (for most parents on most days) cleaning up after messy children. All preaching about how you really ought to feel fulfilled by stuff like that aside, most people don't, yet it doesn't ruin their lives to keep doing it day after day.
Re: Ask HN: Are most of us developers lying about how much work we do?
#374Earlier quoted context omitted.
> I know a few of those developers, and they sit right near me... In fact, this is so common that I can name the exact people at several jobs I've had. And I could mention them to my coworkers and they'd know exactly what these people's reputation are. Our feeling toward them is a mix of being impressed and being embarrassed. Impressed because there's something to be said for someone who works the system to their adv…
> Embarrassed because it's hard to understand how they couldn't be more ambitious at work. Boss makes a dollar, I make a dime. That's why I'm poopin' on company time. Most companies don't meaningfully incentivize ambition. At most companies, even tech companies, if you save them a million dollars you'll be lucky to get a used Red Lobster gift card. If companies want ambition they should incentivize it rather than onl…
Also for a lot of companies millions isn't a lot when profits,expenses,revenue are near billions. I don't really worry about cost savings anymore, the numbers are so huge all around, individual impact is always almost a rounding error.
Re: Ask HN: Are most of us developers lying about how much work we do?
#375Earlier quoted context omitted.
60 hour workweeks are absolutely sustainable? Desirable maybe not, but I’ve known lots of people who have worked ten hours a day six days a week. Especially if they don’t have other commitments.
I think 60 hours of debugging a compiler is different than 60 hours of wining and dining executive clients.
Re: Ask HN: Are most of us developers lying about how much work we do?
#376Who supports the running software, who writes the code for new features, bug fixes and upgrades? Who works on planning and figuring out what to do or not do next? Who works to mentor and train and ramp up new employees? Who does the work to decide if we need to hire more, how we need to break up the work, where we need to invest more, etc?
My work experience has always involved all of these things needing to get done and never having enough people to do all of it.
Re: Ask HN: Are most of us developers lying about how much work we do?
#377I've been a software engineer and managed software engineers for 20 years and worked in all kinds of businesses. This is both normal and mostly acceptable, in my professional opinion. Doing just as much work as your employer requires and no more is way less of a problem than employees who actively steal, commit fraud, bring drama and distract other team members, or are introducing defects because they've faked their…
>However! I will say that this way of working and living comes with some significant hazard to your mental health. Doing something you don't like, care about, or believe in for decades long periods of time can really mess with your sense of self worth and happiness in life. You only have one life, do something with it that is satisfying. Get out of the rat race. This is where my comment about remote work comes into p…
- the build phase: develop spaghetti code
- the maintain/insurance phase: maintain the spaghetti code and keep it up to date with the software package dependencies required by the spaghetti code
In the long term its easier/cheaper to have the person who originally wrote the spaghetti code be around to maintain and add one off small feature improvements to it (i.e. ensure log4j patches are handled properly) than to find/hire/train a new developer every time a 0day patch needs to be applied.
Re: Ask HN: Are most of us developers lying about how much work we do?
#378Many's the day I've been sat in an office, reading Facebook on repeat, present in only the most physically literal sense, because my brain was not going to go into productive mode and trying to force it would be asking for a headache. But the cultural rules of "work" don't allow you to say "not today".
Re: Ask HN: Are most of us developers lying about how much work we do?
#37958 minutes after posting, your post has 134 points and sits at the top of Ask HN. I think that answers your question a lot more clearly than the comments themselves. What you've said is clearly resonating with a lot of readers, even if they may not say so in the comments.
Yes, but they're upvotes from people browsing HN on a work day. Don't think of it as a particularly random sample of programmers.
You do realise the world (and time zones) extend beyond New York and Los Angeles don't you?
Re: Ask HN: Are most of us developers lying about how much work we do?
#380Long time manager here. I call this "work-shy" and it is neither ubiquitous nor rare, I'd guess about 10%-20% of all employees, and it's certainly not unique to software or even to white-collar work. You should think of this as a problem. Even if it's not for your boss or your teammates (and it will be, eventually), it is for you. It is soul-crushing to fill up the hours. Two pieces of advice: 1) The "good" solution…
It is interesting the number of people who see this as a problem that needs to be fixed. Since this specific comment is near the top, I might as well address that here. Why should I work more? How will that improve my life? My self-worth is derived from what I do outside of work to the extent that I don't prioritize professional validation. The primary reason I work is for money. I make enough money that I can live a…
It's possible that you've got cause and effect the wrong way round: consider maybe that your self worth is derived mostly from your extracurricular activities because you're failing at work. You put almost no effort in, achieve very little, are almost entirely disengaged, but, since you're a normal human, being a loser doesn't fit your self-image so you look to find meaning elsewhere in areas where you are engaged, connected, even passionate. It's a coping strategy.
Finding meaning at work doesn't mean you no longer get to derive self worth from your family or your hobbies, rather it just enlarges the pie of your self worth.
The advice given in the comment you're replying to is to find a job or career where you will be able to apply yourself. It really isn't bad advice. You should work more because you cannot exist without working, and what you're doing now is damaging yourself psychologically.
Now I'm not trying to be mean here. I was in your shoes VERY recently. I suspect you've got yourself to a point where a couple years of pandemic stress and working from home has disconnected you from your colleagues and your company and you no longer want to reconnect. Whatever mission you are working towards was probably never all that engaging for you, but take away the human connection and that's been laid all too bare. And I expect you're worried about this ending, and having to go back to a grey office and a shit commute and losing the freedom that you think you have today. You don't want to "lean in" (as awful managers would say) because you recognize the mission as unfulfilling, but you can't separate yourself entirely because you need the money. It's not healthy.
It could be time to take a risk and move. You know you can work remotely, there are jobs out there. There are better missions, companies with values that perhaps align closer to your own. That's scary, but finding a new gig where you'll have to work will not erase all the progress you've made in your hobbies and domestic life; those are things which make you more rounded, and they're yours forever. You can keep up with all that - because, after all, you're mostly just wasting time on the internet today.
I say all this as someone who's struggled with your situation in the past and made a move recently to tacke it. It was frightening for me. I will say that I am considerably happier when my days are full of work, and it hasn't got in the way of any of my side projects or interests, which are numerous and very consuming. If anything, it is more energizing.