2 ms·
I used to be that workaholic who worked crazy hours and had "passion" for the job. Thing is, it's not sustainable in the long run no matter how much you love i
by rleigh 6y ago
I used to be that workaholic who worked crazy hours and had "passion" for the job. Thing is, it's not sustainable in the long run no matter how much you love it. It might be OK in your twenties. But you're not going to be doing that for four decades. You need to live a life outside work as well. Otherwise you'll be a burned out wreck with crippling RSI.
For the record, I did get crippling RSI in my early thirties and this forced a drastic reevaluation of my priorities. Eight years later, and the RSI is manageable but only because I completely changed my lifestyle. Part of that is only working a regular workday, and doing other stuff outside that time. Like running and mountain biking. I quit my "second job" as a Debian developer and general open source contributor because of that. I still do some, but it's strictly casual with no commitments. That's the price for not being physically crippled. You've got to consider your long-term health. Sitting at a desk is terrible for your body. Doing it in the evenings as well is even worse.
Regarding not looking desirable. I think you're a bit off about that. Sane people and sane companies do not work themselves and their staff to death. They want people to be able to work over the longer term, and not burn out. In most of the places I've worked at, working out of hours has been strictly frowned upon. If you can't do your assigned tasks within work hours, that indicates a management failure in assigning you too much work, or in underestimating how long it would take, or in overestimating your capabilities. There is a reason we do all of the sprint planning and backlog refinement. It's to ensure no one is over- or under-worked over the long term by having a consistent and (most importantly) sustainable workload. If someone did find themselves having to work longer hours, the first thing they should do is tell their manager and get the situation fixed. Not to pull out all the stops and burn the midnight oil.
The younger me would have been that person. But part of getting more experience is learning to say "no". No matter how much work you do, there will always be more work the next day. And you will rarely be thanked or acknowledged for going above and beyond the call of duty; ultimately you have to look out for your own self-interest as well as the interests of the company. Sometimes there are good reasons to work overtime, but that should never be a routine part of your existence.
My personal experience of people who work crazy hours is that they wear their "heroic" efforts like a badge of honour, but the work itself is often terrible. (And I include myself here.) When called out upon this during code review, you get excuses like "yes, but it was 2am on Saturday". "OK, but it's Tuesday now, why didn't you review it in the cold light of day and fix all of these obvious defects? We don't lower the bar just because you chose to work late while very tired."
Keep yourself healthy and sane for the long haul.
- cutemonster 6y ago> but it's Tuesday now, why didn't you review it in the cold light of day and fix all of these obvious defects? Did someone react like that for real after 2am Saturday work? (sounds a bit callous to me also when 2am was a bad idea)
- rleigh 6y agoIt's extremely paraphrased and slightly exaggerated, missing some of the context (intentionally, because I don't want to break confidentiality). It was an attempt to provide an example of why working long hours is not a good idea overall. More often than not, work done in a rush, while tired and sleep-deprived and not thinking straight, is of poor quality, and I don't think it's in our interest to lionise "heroic" performance when the end result is not acceptable. More often than not, they would have done a better job if they slept on it and picked it back up in the morning. Or, at the very least, carefully reviewed their work in the morning and fixed all the defects they introduced during the night. Ultimately, every code review needs to be held to the same high standard, and the circumstances of poor quality work should not be used as a justification for submitting or accepting bad work.
- disgruntledphd2 6y agoThat's probably not the best way to frame it, but it's important to make people aware that they can't work 60 hours at the same quality of the first 30. Even if they could, they'll either burnout, get promoted or leave within 24 months and then you'll need to backfill with multiple people. Even as an evil manager, you're still better off stopping people from overworking, as you'll get more work overall from them at a sustainable pace.