4 ms·
That team lead (and companies with similar thinking) need to learn that obsessive/workaholic devs are not more productive. If coding consumes your paid and fre
by smt88 7y ago
That team lead (and companies with similar thinking) need to learn that obsessive/workaholic devs are not more productive.
If coding consumes your paid and free time, you're generally not cranking out new CRUD features requested by the marketing team. You're doing pet projects, learning new languages, or getting lost in bikeshedding, like writing a new JS framework because you think the current list sucks.
That means your workaholic employee is burning out on things that don't help your company, and their actual paid work is probably a distraction from what they really want to be doing.
By contrast, someone experienced with a family and/or hobbies working 40h will often do their work well and have ways to detox from work problems before getting started again the next morning.
A lot of that is my anecdata, but hiring people who want work/life balance is working so well that those are the only devs I have (14 at the moment).
- renewiltord 7y agoI'm somewhat amused at this rejuvenation of the age-old belief that folks who have this as a hobby are somehow maladjusted and burning out. Fascinating. I think it was this early belief in the 90s and then the dotcom boom had the superstars and then the next wave had the next superstars and it shifted. Now it's shifted back. Wonder what shifted it. Well, to my people out there, do not fret: there are still places to work where you work with other obsessives, there are still people who look for that in each other, and after 20 years of messing with computers I can tell you it is still joyful. You can do what you love and make a lot of money doing it. And in these places no one will judge you for loving the thing you work on so much you do it for fun as well.
- smt88 7y agoYou've missed my point entirely, which is perhaps a communication failure on my part. I believe there are obsessive coders who will have lots of money/fun. Some will be valuable to their employers. No company should only look for these coders, which is the policy I was originally trying to refute. It's much, much easier to find productive 40 hr coders than productive 80 hr coders. The ones coding for 80 hrs are often perfectionists, or they believe they're immune to burnout. You yourself seem to believe that loving something enough means you can avoid burnout. You can't. Burnout is part of our physiology. If you lose even small amounts of sleep for long periods of time, your performance falls off a cliff. What's worse is that you don't know you're not at your best. Look at pro gamers. They love games enough to play them all day, every day, but they still suffer at the end of a long session.
- ramraj07 7y agoGeneralizations galore on both sides? There are probably as many 40hr Devs that just want to phone it in as there are effective ones. It's possible youve learned to weed out the former but they do exist. Similarly I'm probably one of those Workaholics, but I make an active effort not to waste time. However I do work with good effective 40hr devs and I try to make sure that we are all on the same velocity. The remaining time I spend on pet projects for sure, but I do hope they are not a waste of time for someone, be it my personal growth or my company.
- watwut 7y ago90 hour a week means that the person is either not sleeping enough. Sleep deprivation means you cant be performant fully. Or the person did not had a single free day in weeks while working 12 hours a day. There are the people who do stupid decision just out of being tired. Just about the only way I have seen people work this much and not be overly tired drag was when significant bulk of time was spent socializing and playing around. Otherwise said, it was not actually work, but it was clocked in as work. And at this point, there is enough evidence that crunch is productive for few weeks and then productivity fails.
- ramraj07 7y agoNot sure where these numbers come from. I come from acadrmia. The expectation (and for the most part, reality) for someone in track to become a successful tenured professor is to maintain 80 hr weeks for a couple of decades if not longer. My professors maintain this still, it's how they live now. They have kids, but they had them when they're in their 40s after getting tenure. And they are not working below optimal intellectual abilities. You would be surprised at what your mind can do if you want it to. I made the jump to tech from academia because while I was ready to do that insane work ethic I wasn't convinced that academia as it is today was worth it. Turns out I can't just switch off this style of working though, and hence I end up working harder than I should. I'm not wasting my time though. What I have observed though is when engineers who are in their twenties just Naturally go into an insane work ethic without mentoring on focus and time management typically waste their time. But it is possible to be 2-3x more efficient by increasing the hours you put in as long as you are smart about it. Many of the smartest people in the world do. Of course this should be a personal choice. 90 hours is a bit much though. 80 is probably the sustainable maximum for any normal human.