126 comments

[ 5.1 ms ] story [ 251 ms ] thread
I think this is a pretty mainstream view, not sure it would be considered contrarian at this point. Not to say it means that everyone has moved on from a culture of long hours. But I'd say quality over quantity is a pretty easy sell nowadays, the harder question is how to get to quality. Long hours seem more like the thing to do when you don't know what else to do.
Since I started working for myself, I do find periods of time where long hours are the norm. Most of the time I stick to a more regular schedule, but when I was building an MVP I put in long hours because taking a break meant having to re-learn how all the code went together. Once I had made the various breakthroughs, I backed off again.

Then later, when working with our first customers I found myself working long hours again.

Now I've backed off again somewhat.

So I don't think it's necessarily "when you don't know what else to do", for me it was driven by either not wanting to miss an opportunity or trying to hit some deadline.

Most of the time now I can choose when to do that, and often find it's more productive to be contemplative about things like new features rather than doing them in a hurry and having to do more refactoring later on. Then again, in some parts of your business cycle you simply don't have that luxury.

That's fine when working for yourself, you clearly stand to gain by putting in longer hours from time to time.

I recently resigned from a job where it was becoming clear the business wanted to set unrealistic deadlines and just expected devs to work extra to meet them. This company didn't offer shares or even have a bonus structure in place.

It is not ok to expect your employees to work extra to meet your (frankly unreasonable) deadlines when they don't even stand to gain anything from it.

I agree with that. Its partly why I quit a job like that myself.
>That's fine when working for yourself, you clearly stand to gain by putting in longer hours from time to time.

I'm not so sure, I suspect all the reasons it's bad for an employee are equally true for a founder.

Yes, probably. But at least in the founder's case, they stand to materially gain in a big way if they succeed, so the tradeoff may be worth it someday
(comment deleted)
I was excited to read an article of someone saying that long hours is actually good aha

Still a well written and thoughtful post.

> Long hours seem more like the thing to do when you don't know what else to do.

No that would be your mum

It's mainstream, but specifically among laborers. Managers, and particularly executives, still seem to overwhelmingly disagree. And guess who sets the rules?
It's literally the mainstream view...
Yeah this article definitely makes Silicon Valley look like a huge bubble - to the point where one feels "terrified" to write a post saying "maybe long working hours is unnecessary".
Bragging about the long hours you work is a (ironically low effort) way many people self-promote how valuable/important they are. I've noticed these people often do not mention exact what they've accomplished with all these hours, just the hours themselves are mentioned.
Outside of a certain circle that's described in the post, I think "working too many hours has diminishing returns in the short term and big problems in the long term" is pretty mainstream.

But I haven't seen other people promoting "take short hours as a positive signal and long hours as a negative signal for making investment decisions" like this post. It's usually more "that's not sustainable" then "that's a sign you might not have exactly the right fit."

I think that's a fairly novel take and worth further thought.

I'm at a FAANG where people work really long hours (working on weekends/till 8 pm at night on weekdays are a normal occurrence) and we have some execs that really value butts-in-seats/gotta be in the office type mentality and are very excited for return to office.

I struggled with the culture for a long time because I naturally don't feel inclined to be in a distraction riddled office or work long hours. I find the stuff I work on outside of my job to be more interesting. I realized that the way I want to add value is by working smarter and by continuously focusing on high-leverage projects. If I get ostracized or penalized for not working long hours then so be it. I figure that I could always switch to a different team or company.

I'm glad the author is writing about this and I hope more places move away from glorifying working long hours.

Are you in the eng side or non-eng? My experience of FAANG life has been 40 hour weeks, with weekends worked on the rarest of rare occasions (none so far this year). But I'm aware that non-eng units have a more brutal time of it.
I’m on the eng side. Your experience is in line with what I experienced when I was working at an Alphabet/Google X company (working weekends was unheard of).
I'll give you an actual contrarian take on working long hours: I like it, and I'm really tired of people commenting on what hours I keep.

I enjoy my work. It's what I'd be doing in my spare time if I didn't need or have this job. I've thought about this, and I think I'd stick around at my role even if I hit a windfall, because I want to see this through to the end, one way or another. Sometimes, in order to do the kind of job I would be proud of, I need to work very long hours. That's 100% fine with me, but it's not always been fine with some other people I work with.

I'll even go one step further; I like working with others who share this view on working. I know not everyone can do as I do, and not everyone wants to do as I do, but when I'm working with people who can and want to work long hours, I am substantially more satisfied at my job than when I work with 9-5ers.

I don't in any way begrudge those 9-5ers, I just would rather work with people who share my ability and desire to push as far as is needed to complete the work to a high standard that is usually not possible in 40 hours a week.

It just seems like I have to constantly kowtow to the 9-5ers because they get so bent out of shape when you suggest that their style of working is only one of many totally acceptable ways of living. "Work life balance!" they shout, but not all of us have bifurcated the concepts. Work and life don't have to be these entirely severed things, I much prefer to weave them together and work with other people who can weave them together successfully.

It's frustrating. There's some sort of moral nobility in "only" working 40 hours, like I'm the problem and they're just trying to live their lives. I don't mind! I just want to work with people who value the things I do.

Good for you, I in no small way envy your dedication to your work (despite choosing to work 30 hour weeks myself).

Would you say the reward is commensurate for your effort?

I'm not necessarily on your side, but I expected the "contrarian" take in this blogpost to be "actually, I think long hours are great!", not "maybe long hours aren't great!"
Me too! I was thinking it was going to be a paean to the joys of working long and hard!
I don’t have a moral issue with it in isolation but it does “throw off the curve” in a system where we are all valued relative to our peers. A student who asks for more homework because he likes it is great, but he is going to draw a lot of ire from his peers.
I hope that you are aware that you are greatly empowering your employer by intricately interleaving your work and concept of life. If your social network, your personal support network, your community and self are tied to your work; then your employer has tremendous power over you.
Two people can have political disagreements without one of them being ignorant.
In principle if two people disagree politically, they are both ignorant. If they were enlightened, they'd agree on a common policy.
People can disagree on which values they want to emphasize without either of them being ignorant.
(comment deleted)
This is a needlessly adversarial take. An employer that values you will empower you with commensurate compensation.
Hardly needless. Employers throw out faithful and dedicated employees all the time, even in ageist industries where it is difficult for them to find another job. I saw this happen to a close friend's father; their financial stability crumbled. He seemed to have aged 10 years overnight. It was quite a few years before I saw him not visibly depressed. Despite being a talented engineer (not in software) he never found an engineering job again.
How is this relevant? Presumably the reason we’re discussing bc in this thread for working longer hours isn’t job security, but job satisfaction. I don’t see how this connects, frankly.
I was responding to a comment that spoke about employers who value employees as if this is always clear to employees, or even true in the long run.
In an employer throws you out, then they ostensibly don’t value you enough to keep paying you.
hahahahah this is good!
They absolutely will not. They will pay you the minimum amount they can to keep you around which, if you love your work so much you’d do it for fun, isn’t a lot.
An employer that values you will empower you with commensurate compensation.

If someone on my team chose to work 80 hours a week because they loved what they do then I would actively discourage them, and remove them from the team if they continued. Having someone like that around has several negative impacts;

- It makes other people resentful of the fact they have to work longer hours, or change their schedules, to keep up with features or testing. That leads to more staff churn.

- It's harder to have discussions about the work being done when someone is working outside of office hours, which leads to things being done as one person sees fit, or needing to be reworked often. That annoys other people on the team.

- Other people on the team who choose not to work more than their contracted hours would be very annoyed if they saw hours as a factor in compensation, leading to more staff churn.

- In a small business that charges for time in days, someone working 16 hours a day is essentially giving the customer work for free. If you charge for 2 days work, and tell the client you're doing 2 days work, but only work 1 day, that's dancing around the edges of potential fraud. A client could very reasonably argue that if you did the work in 1 day they should only pay for 1 day...

I would much rather have a good team of people working well together than have one hero doing most of the work.

> If someone on my team chose to work 80 hours a week because they loved what they do then I would actively discourage them, and remove them from the team if they continued.

So you don’t value this behavior - you view it as a liability to your team, for the reasons you outlined. None of what you have stated contradicts my point.

> - It makes other people resentful of the fact they have to work longer hours, or change their schedules, to keep up with features or testing. That leads to more staff churn.

It shouldnt do though, your team should be able to work any number of hours and still be productive because things like illness, pregnancy, deaths, holidays occur and they are not always expected or planned.

> - It's harder to have discussions about the work being done when someone is working outside of office hours, which leads to things being done as one person sees fit, or needing to be reworked often. That annoys other people on the team.

Depends on the role the person is doing, a good team will be able to cater for those who do more hours, just view that person as like two people working then you can see your team is incapable of working with two people performing a task/job.

> Other people on the team who choose not to work more than their contracted hours would be very annoyed if they saw hours as a factor in compensation, leading to more staff churn.

Seems like a rehash of point 1 and that shouldnt matter.

>- In a small business that charges for time in days, someone working 16 hours a day is essentially giving the customer work for free. If you charge for 2 days work, and tell the client you're doing 2 days work, but only work 1 day, that's dancing around the edges of potential fraud. A client could very reasonably argue that if you did the work in 1 day they should only pay for 1 day...

Then you have a contract issue which is not handling your charges properly. Flip this around, what if you got super busy and had to do 16hrs a day to complete the job more quickly to get onto another project/source of income, would you still work 8hrs because you contract charges are wrong?

> I would much rather have a good team of people working well together than have one hero doing most of the work. I sense you despise individualism which might explain why so many people go work for themselves.

Seems like a rehash of point 1 and that shouldnt matter.

I'll clarify then. Point 1 is that people get annoyed having to work with someone who puts in more time because it makes their work harder. Point 3 is that if people see that someone got a raise or a promotion because they put more hours in, then they will think they won't get a raise or a promotion unless they put more hours in. They will see working longer hours as the barrier to advancement, and if they don't want to do that they'll leave.

I sense you despise individualism which might explain why so many people go work for themselves.

Saying I "despise individualism" is a bit melodramatic. I've run teams for the last 20 years or so and I've enough experience to understand that a good, well-motivated team of devs who communicate well and collaborate on a common goal is far more effective in the long term than a team who have a lone dev who's happy to grind out code in the middle of the night.

I see where you are coming from which is you want a team, which is understandable but that doesnt work for the individual whose happy grinding out code in the middle of night aka the lone wolves, but then would they be working in a team in the first place?
would they be working in a team in the first place?

If you're a dev who works alone, with no other devs, no product person, no QA, no support, and no users to collaborate with then you probably can just hack on your code for however long you want without bothering anyone.

> It makes other people resentful of the fact they have to work longer hours, or change their schedules, to keep up with features or testing. That leads to more staff churn.

It is more of resentment of lower quality of output and a lot wasted time while looking like super hard worker.

People who work 80 hours a week dont have actually higher output. They get tired , myoptic and they get all their socialization in work. That means a lot of wasted time for everyone around while acted offended on suggestion that he/she is not the most performant person around.

And yes, this was repeated observation.

That's certainly true of some devs, but I've also seen devs who don't have that problem. Some people genuinely can write good code all night long for months on end. That's why the points I outlined aren't about the individual dev. The impact on other people is still bad even if the dev is great. All of my reasoning about why I don't want 'heroes' come down to preferring a strong team of good devs over a good team behind a brilliant dev.

Plus, if you want to make this about individualism and maybe stray into a little game theory, if a team has someone doing loads of more work than other people, one day that person is going to leave and your team will suddenly take a massive hit in productivity. That makes everyone on the team look bad. Everyone does better when there isn't an outlier (apart from the outlier, obvs).

> Some people genuinely can write good code all night long for months on end.

Yes. What they can't is do it all night long and all day long for months on end.

There are people whose hourly output is twice as múch as normal. I would even say that hourly output variation is much higher then "how many hours per week you are effective" in terms of output. And none of the "people angry because they have to test too much" ever happens.

Yup, from experience, you can pull this off for maybe a week or two before you start causing problems or negative output, or get actual health issues. And that's if you're young, older people tend to fall off sooner.

The clincher is that you're never getting paid for the extra effort commensurate to it.

Name one case where this has been true. It's not the case at any business, even ones with the lavish funds to do so. Just about everywhere, new hires will be making more than tenured employees of comparable level regardless of their expertise and proven value.
Yes, they benefit substantially from my work, and I benefit substantially from doing work I love. Win-win. Not sure what's wrong with that. Besides, I don't just trust anyone, the people I work for now have earned that trust over time; I want to see them succeed, because I succeed when they do, and vice versa.

They are capable of causing me harm due to that trust, yes, but that's what opening yourself up is. If that happens, it will hurt, I will recover, and I will find a new way to mesh what I love with what I make money doing. It would suck, but I would survive it.

You would have him subvert his motivation away the source of his contentment for something as abstract as benefiting the quality of the network of relationships?

Quite literally arguing against the individual in support of a network: hivemind. It seems like you’re forgetting you’re talking to an individual.

I’m for people working a lot if they want to and it makes them happy, but humans are inherently social beings and community is incredibly important to our mental health. OP (of this thread) even says part of what they enjoy is working with others who similarly value their work.

It doesn’t make sense to wave away social needs as some trivial or “abstract” concern.

Sure if you can theoretically weave life and work together that's great I suppose , but for some of us that would be exceptionally difficult given our interests and priorities.

I can't interweave my ability to sit down and play guitar and piano, swim, go on hour long hikes with my dog, juggle, study Chinese, and write dnd campaigns. These activities are not conducive to your "blended style of work/life".

additionally it's all about compensation as well if everyone was working overtime then it sort of normalizes it.

As frustrating as you find it, I find it completely baffling that people have such single minded interests that they would choose to pursue just one thing more than 40 hours a week.

The fact that you're posting some giant message about how much you work means it's unlikely you are truly working as many hours as you think.

Use a tomato timer and hit the "Start" button every time you're truly doing work and "Stop" button when you're not. Bathroom breaks, employee chats, heating up lunches, break walks, posting on HN, etc... All that shit doesn't count.

Get back to us with the #s after you've done a sustained run for a month.

I completed 32 pomodoros last week, which is above my average of ~25 for the past year and change, and a lot of my job isn't focused work, and none of that pomodoro time included any of the project management, meetings, or conversations I had with the team to figure out what we're up to, what the problems are, and what we're doing next.

But that's not the point. The point is the 9-5ers have held the higher moral ground for years now, and I'm tired of having to apologize or justify my preference for longer work hours because it makes them feel bad. There's nothing wrong with what their work/life balance is, but there's also nothing wrong with what my work/life balance is.

Honestly it's not that bad if you work weekends. You still have plenty of time to do other things, you just can't get as into your hobbies as you might like. I had to quit my WoW raiding team to devote more time to this job, for example. I don't think anyone would argue my decision there was a huge loss, and honestly the ~15 hours a week I was dedicating to WoW is much better spent on work and work related things.

I'm definitely procrastinating right now by typing all this out, so this time doesn't "count", but it's usually during my 5 min breaks between 25 min sessions, so I don't consider it lost time.

Is 32 pomodoros equal to 32*25 = 800 minutes (13h 20m)?
Something doesn't add up with their comments does it.
A pomodoro is four 25 minute sessions with a 5 minute break between each session.

One "pomodoro" takes 2 hours to complete.

That makes 32x25x4 = 3200 minutes (53h 20m), which is a significant amount of time for focused work.
You're telling me!

On top of that I was doing the various agile meetings too, it was a lot.

Normally I do 3-5 pomodoros a day; one early in the morning, one to three during the day, then one late at night after the wife has gone to bed. I don't really take days off, so that ends up working out to a pretty decent clip, all things considered.

That's an incredible pace, especially not taking any days off. When I do so, I lose my sense of time. I feel like, I've been working forever. I have to switch to a different task for at least a day to recover.

Do you have to maintain a certain sleep schedule or do you happen to naturally find it easy to work at this pace? How could I train myself to work as intensely?

Last week was rough, but generally it's not bad to do 3 pomodoros every day and usually I'm rolling during the day so it's fine to slip in the 4th.

Same with the evenings, and then I'll get 5 in which is a very productive day. Normally it doesn't really require any less sleep or even that much less time spent doing other things, I think the trick is working every day.

> The point is the 9-5ers have held the higher moral ground for years

This has nothing to do with moral high ground.

People get mentally or physically exhausted after a normal day of work. You are the exception apperantly. Since I cannot find what you actually do I'm going to count it as a very easy job with no mental of physical exercise required.

(comment deleted)
What type of work do you do?
I wear lots of hats right now; I was employee #1 so I did whatever engineering needed doing to get our platform created and functioning. Frontend, ops, backend, selecting vendors, eventually hiring, working on compliance, helping define strategy, project management... basically anything that needs technical expertise I'm leading.

...and I'm loving every minute of it. I committed to seeing this through at least until they don't need me anymore, and I fully intend on meeting that obligation, and possibly well beyond that if the work continues to be fun.

It seems pretty obvious that you work at a very small company with little or no layers of management, and most likely, without any other typical constraints that most workers deal with -- like fixed hours, an inconvenient office or commute, lots of unproductive meetings, limited amount of annual PTO, lack of knowledge/understanding whether anything you do has actual impact at the company, etc. Putting in 70-80 hours week after week in a scenario like that where it's very clear you're simply an employee is pretty crazy. But for a passion project, where it's just you and a few close friends/coworkers, sure, go for it. Hell, for about 3-4 months during Covid I was easily putting in 90+ hours on a project I loved working on. It's not really as heroic as you're making it out to be.
Not sure why you think I believe it to be heroic, I just think I shouldn't be shamed for spending my time how I want to.

You'll note how the shame is being attempted in this very comment thread. It makes me sad. :(

I think "shame" is a needlessly inciteful description. The main issue is that, in a company with multiple employees, your behavior is not happening in isolation. When one person is working 80 hours a week, it is very common for management to see everyone who chooses to structure their time differently (e.g. because they have kids or elderly relatives to care for) as a slacker.

If it turns out that management is not thinking this way in your company, then great! But I think most people commenting skeptically here are familiar with situations where one over-achiever in the team sets an impossibly high standard for everyone else and thus unwittingly causes them harm.

This is also why it is usually not considered a problem when a person pursuing their individual passion project puts in crazy hours. If you work for yourself, you're not setting standards for anyone else.

He is just working himself to death making somebody else rich and thinking that this is a win-win situation. It would be hilarious if it wouldn't be sad. Also he seems to be working in a startup which means he will most likely go bust and all his work will have been for nought.
The simple solution - work two jobs. I don't care if you work 80 hours a week. I don't think it's healthy or sustainable, but maybe it is for you. And I certainly don't think your fatigued work it's as beneficial as putting in a good 40 hours. But feel free. There is no reason it has to be the same job. Make two sets of 9-5ers happy.

Meanwhile, if you set a standard that makes people expect your coworkers to work 60 hours a week, expect them not to like that.

Simpler solution: work with people who share my values.

This isn't theoretical. I'm currently doing it, and it's immensely fun!

Out of curiosity, I wonder about two personal questions. How old are you and how are you compensated for the extra hours? I'm not sure you're willing to share, but if you're working 60 hours you should have equity or extra pay.
I have equity, yes, and I'm not comfortable talking about my age but I will say my wife works harder than I do and we don't have any children.
You’re not comfortable talking about your age? Why not? Can you just give a broad range?
He's not comfortable divulging that. Let it go. I understood and expected he may not want to share either of the things he expected. Declining information about yourself online is reasonable and requires no further explain action.

I mainly was curious if he was young enough he was burning himself out and the burn out hadn't caught up to him.

Saying “I am under 30” for instance is hardly divulging anything that could possibly be sensitive.
Heck, putting in a best 20 hours is often better than standard 40h of which a lot is stalled or peak focus is out.
> I want to see this through to the end, one way or another.

Would you be OK if you were terminated for an unjust reason? If so, that's great. If not, that might mean you have other expectations than just working on the problem. I would reconsider my strategy in that case.

It's weird, but I think you are right. For context, I worked like you for most of my career and only recently joined a scale up that has very strong work life balance. It feels like the people don't care and I am demotivated. When my tech lead told me that if he'd be expected to work overtime he'd quit (he's great otherwise).

I kept telling myself it's good for me because I have a baby now, but the truth is I found another job to do over evenings and I feel less and less motivated at my day job. When you say that you enjoy working with people that are not 9-5, it resonates strongly.

Enjoy it while you can. Realize though that being "employee #1" and wearing all the hats while working with others that "share your values" means they probably think they themselves are "employee #1" and wearing all the hats, which obviously can't be the case in a well functioning team.

I'd hate to see how that works in a large project - like SpaceX where teams have to build things.

IOW, consider you may be better off running your own show while you have this drive. And realize you'll want to hire the best and brightest regardless of their WLB preferences.

Currently it sounds like all the effort you are spending is in service to someone else's vision, and it better have equity involvement on your part because you WILL get interested in other things and unless you've built a war chest for your own ambitions, your work will be for nothing when you inevitably walk away - hopefully to do you own thing.

Don't make the mistake that your employer has your long-term interest in mind. It's not personal, it's just business. It's always what have you done for me lately

>>I'd hate to see how that works in a large project - like SpaceX where teams have to build things.

I'm not sure using SpaceX is the best example here given that they were (still are?) notorious for their grueling work hours [1][2]. If anonymous social media posts and Glassdoor reviews are at least a rough proxy, it seems that the hours are still long but trending down from 80-100hrs per week to something "more sane" like 50-60hrs per week [3].

[1] https://www.vice.com/en/article/9a39av/a-spacex-employee-jus...

[2] https://www.vice.com/en/article/mgbnwp/the-odd-empathy-of-el...

[3] https://www.reddit.com/r/AerospaceEngineering/comments/oho00...

[4] https://www.glassdoor.com/Reviews/SpaceX-long-hours-Reviews-...

(comment deleted)
I agree with you, and based on how adversarial the comments are on this comment, I think you have the real "contrarian take on working long hours."
Mark my words: in a matter of years, you're going to be a husk. Ask me how I know.
Many of us "only" work 40 hours at our paid employment, but do loads more hours for our other jobs:

- Maintaining our relationship with our spouse

- Caring for our children

- Contributing in our community (neighborhood, friends, church, hobby group, open source project, etc.)

---

Those coworkers who get bent out of shape are probably concerned that you're raising the employer's expectations of their employees.

They may also be concerned about you personally. Your coworkers may feel that putting so much time into your employment is unhealthy for you, even if you don't realize it. From their point of view, they can't understand how you can work like that and be healthy and happy. To you that may feel annoying and judgmental, but it comes from a place of concern and care.

It's the other way around. You think there is "nobility" in working more than 40 hours a week. There isn't. Stop pretending.
I went in prepared to read the "contrarian" take that working long hours can actually be good, but it is just stating the obvious.

Working for over a decade in silicon valley, I have yet to come across a company or group where the majority opinion has been that people must work more than 8 hours a day to succeed. I'm not sure if there ever was a time when overworking was a norm in the industry, but it definitely has not been the case for a while.

Heck multiple companies, including Amazon, are starting to experiment with 4 day work weeks. If you are in a position where you must justify (to yourself, management, or the public) a regular work schedule, save your energy and just quit.

> have yet to come across a company or group where the majority opinion has been that people must work more than 8 hours a day to succeed

I've absolutely worked at companies where this was either understood but not spoken or was clearly espoused by leadership. I don't think it's rare at all, at least within a certain crowd of successful companies.

I believe that most management just want people to do more work for the same amount of money. It's less about how many hours are necessary to succeed, it's about "how much more can I squeeze out of my employees."

Those companies that are experimenting with work schedules are also trying to squeeze more out of their employees... just in a different way. They may recognize that causing employees to burn-out is a problem and are looking for ways to optimize the employee output.

It isn't necessarily a bad thing to optimize for employees generating better output. It's only bad when employee morale is completely ignored.

The pattern is very simple: status update and collaboration meetings grow to consume the official workday. Perhaps not 100% cover, but with few and short enough gaps that you can't really work in them. To the extent that your survival or advancement at the company depends on actually doing some work (this is not guaranteed!) you need to do it on your own time.
Yea this comes to the poor alignment point.

I recently left a company where I led a team in building a high quality and very complex product but the job felt super easy.

Now at my new gig I'm managing a new team where the product is garbage and the team is very junior. Neither of these are the cause of my overwhelming workload as the ultimate product is very low complexity. It is instead the horrible alignment of various personalities that results in an inconceivable amount of meetings and daily shifting priorities.

Wait, what Amazon org is doing 4 day work weeks? Not that I have a particularly rough schedule, but it could always get nicer...
I think that mostly I agree with the author, that there is a religious following of the long hours/never sleep work model. What has worked for me, as I am over worked and spend far too much time on meetings at all off hours, is flexible hours instead of rigid ones.

My day blends a lot more, as I have periods of work and periods of "life". Instead of a rigid 8 hour block, work is just one of those chores I do, and I align blocks of time much like I would for cleaning the bathroom, getting groceries, zoning out on a show or a run, etc.

This means a lot of breaks and no-work times, and a lot of responses and participation at times when colleaguss in other regions don't expect it. It kinda works for me :)

The impression is that I never sleep, but in reality, it's just I am distributing the work hours far differently and I can get s lot more done this way. 1.5 hours in some morning over coffee for email, scattered calls throughout the day, in the evening set aside some time after dinner and exercise for some project work (actual coding or just thinking about it). Sometimes I just merge it with other activities that don't need my full attention (is it an evening walk or a planning session if I think about a project while walking?)

I am very lucky I have this flexibility, and I know it is not a universal thing that everyone can get, but not having such a rigid structure let me really break down my day to work the way I need. I still meet all deadlines, meet all meetings, and I define when I'm not answering emails or messages. It rubs some people the wrong way as they never know when to plan meetings that involve me since they rely on outlook scheduler, and unexpected meetings tend to not happen as often (which is good for me :) ), but ultimately I like having more control over when I allocate work time

I used to be one of the people that were ascribed the "talented" label. It opened a lot of doors, and I've had a career that initially was deemed as more successful than that of my peers. However, after burning out twice I've never recovered the ability of doing _anything cognitive_ other than physical exercise for extended durations of time. I no longer get called talented, and things are a lot more challenging --- and I'm more afraid to go after tough tasks --- but I still manage to get things done. It's just that I need a lengthy break after 2-3 hours of being cognitive.

Your comment semi-accurately reflects how I lived my life _before_ burning out. I sussed out when I tried to do a more 8-5 kind of thing. But I struggled to fit a lot of things other than "work".

It also could be age, not just the fact that you burned out twice. I definitely have less cognitive stamina than I did ten years ago. Who knows if that is age, pandemic-isolation-related, or what.
I get that. For me this works because I gave myself permission to do what I think US culture (where I grew up) forbids us to do; set clear boundaries.

Not acting rude or harsh to people, but instead just being honest and protective of our time, both work and personal. I do have a reputation of being "difficult to work with" from some people, but almost universally those who have that perception are the ones making heavy demands on my time because they themselves cannot influence the resolution. Sales managers, customer success managers, they spam meetings and unplanned calls and emails with no more content than "this has to be resolved yesterday" and other cliches. I have no qualms just outright ignoring them or calling them out for violating procedure/policy.

The same types that just want to keep a channel of updates open and to help buy time? Much better relationships as they understand the process more and respect people's time.

Basically there is a stress aspect, and it's not for everyone. For me, having those firm boundaries and being honest with myself that this is my time and it's my choice, I don't need to feel guilty for protecting it, it helped a lot

> I gave myself permission to ... set clear boundaries.

My biggest career regret is that I fell into the trap of not setting boundaries for fifteen years. What is clear to many people now was not to me then. Even now, I'm learning the basics like that there are different types of boundaries and in business which ones are most important to set and what happens if they aren't set.

Time-boundaries, for example, are commonly discussed, but equally important are socio-emotional boundaries. Have you ever stopped to realize that you talk to a lot of people daily, but lack emotional support or the deeper connections that come from being emotionally vulnerable? I have. It's easy to surround oneself with work friendships that only ever touch on surface-level topics. Having a clear emotional boundary helps create space for emotionally meaningful connections outside of work. That's a lesson I wish I didn't have to learn the hard way.

+1 to setting time and emotional boundaries. Lasted through way too many different design teams that all inevitably burnt out because the folks there (all very kind, compassionate, talented people) weren't willing to make that a hill they were willing to die on.

Earlier last week, used the metaphor of putting on your oxygen mask "first" in case of an airplane catastrophe, before putting on anyone else's mask, even your child's - think that's quite apt here.

Right there with you, nobody has ever put it in words in front of me before.
Interesting, thanks for sharing this. I'm curious how you know you've "worked enough"?

I find that I'm someone who works well in nonstandard hours and would like to take this approach to work.

At the same time I find the "work whenever" structure very dangerous for me. There's always more that needs to be done than I can fit in a day. It's really easy for me to spending most of my day thinking about work or working, even when I'm doing something else.

Maybe I'm just not built for this kind of work, but I'm curious if you have a technique for dealing with this kind of thing

Sure, for me I focus on a few aspects:

1. What are the high priority projects? 2. What must have my attention? What can be delegated and monitored? What can be delegated and forgotten? What is in our responsibilities and what needs to be redirected? 3. What is a personally engaging project I want to work on to stay excited?

1 and 3 are the ones I get careful about and closely monitor myself to see how tired I am and how my thoughts are; since a lot of my work is not just technical but also communication of this to a lot of persons (internal and external), I take the time to be very aware of my mood and my thoughts and feelings. If I'm feeling angry or grumpy towards everything, it's time to stop because this will bleed into my work and I've worked enough. I force myself to send an update that I will have something more substantial later and a brief summary of where we are at.

For technical items, I kind of let the linter tell me how many mistakes I'm making ;) If the linter is working hard, probably it means I'm just too tired to be effective, and it's time to write down my current thoughts and plans in the next 5 minutes and call it for them, and either rest for the day or relax a little

I constantly violate schedules so task lists and timers don't work for me. I prefer an ultimate deadline and I'll manage my way there. On a day to day basis I just decide what my task list is and the priority and then go one by one.

Hope this gives some inspiration.

I don't think this is contrarian at all. I went in expecting a blog post on "Why working long hours is good".
All comments so far are about how mainstream that view is. But it’s not my experience at all.

Every time I interview for a position, people brag about how dedicated their team is and ask if I am willing to put in the hard work and all. I’ve literally never ever heard any recruiter say: “oh we work smart here, you know. We just spend the right amount of time so that everyone’s productivity is best”.

You may need to interview outside of that geographical area, maybe in Europe. I've been working for a firm that almost verbatim said those words in the interview - and after some acclimatisation (in which I felt horrible for "only" working 8 hours a day), no amount of promised compensation would drag me back.
I think its a sign of the times when super highly paid individuals like VCs have to navel gaze about what the "optimal" amount of time working should be. Business is fundamentally a competitive game and when the free money tap stops there will be a rude awakening.
The problem with long hours is that when applied carefully and occasionally, it sometimes does work.

Say I decide to finish what I was working on before leaving, then run into some difficult problem, finish after midnight having completed the task and solved the problem now and forever for everyone. With those 8 extra distraction-free hours I've produced equivalent output of 3 regulation work days and 2 committee meetings. I win. The mistake one can then make is to think that this can be repeated at will by staying late all the time.

I don’t think this is true for engineering.
This is meta-strange. Bragging about long hours makes someone sound ridiculous, like a humblebrag that is actually the opposite of a brag. But it's also ridiculous to claim to be "terrified" to write a blog post in which 98% of the audience agrees, actually just thinks it's common sense.
I am not in SF but follow a lot of people there. My intuition is a lot of them promote long hours. I also worked in a few startups in Poland and all of them promoted long hours. I think the idea of working hard is real in startup scene, even though posters here might disagree. Take notice of most of us here are engineers, not business people
Is this an American thing to work super long hours?

Most people I know and work with do less than 40 and aim to be more efficient at delivering in less time.

I had a friend who worked in the states for GE and he mentioned people just had to be seen to be in the office for at least 12 hours a day even if there was nothing to do. Is this kind of culture real?

Very real unfortunately. After having worked with US clients now it is one of the things about US business culture that I find problematic. Companies publicly celebrate and reward those who work unreasonably long hours even though this doesn't correlate with actual productivity / efficiency.

It also adds toxicity to the work environment as those working long hours start to have little respect for people that set boundaries. The worst situation to be in is working for a manager who is a workaholic. Despite what they say they will absolutely judge you for setting boundaries and it will affect your career prospects.

People have different styles of working. I have found that if I am deep into a problem, dedicating long hours to solve it is more productive as I have the context for longer time and can try out different things as I am deep in the zone. It is not as simplistic as "they work long hours because they don't have product market fit.". I like to solve problems, engage my brain, and the kind of intellectual simulation I get while working is something I can't get outside of work. I would regularly dedicated 12 hours a day and work on weekends, and when I am out of the zone, I will take a break for a few days, recover my energy and then go back to work.

I had an employer who was exactly like that, so understood it better than others, giving me the leeway. Infact, most of my colleagues were like that. We had our own social life beyond the office, but I did not feel like socializing everyday anyway.

Ah, some stupid Silicon valley bullshit. Programming and many more things done there, is not work. Yeah, it looks like work, but it is not, it does not produce something necessary for biological living or education or life support. It is more like: I like reading, I read 18 h/day. OK, cool.

Work is something that is done to reproduce life. Programming, reading, is not work, it is life activity itself, do it as you like.

Example 2: it does make sense to optimize biologically needed production. But it does not make really sense to optimize life activity. I like cycling, I measure my performance, but I'm ok that some people cycle just for fun.

I love my work and work long hours and some weekends but I hate all the morons I have to deal with at my job.
Ah, the weekly humble brag about working 4 hours a day to millions. People who agree must not be business owners or entrepreneurs or traditional hackers
>Our celebrity role models work very hard: Jack Dorsey ran two companies simultaneously for a while. Elon Musk is worshiped by a massive audience, in part for his superhuman work ethic. Enough said.

Jack Dorsey notoriously got kicked out of Twitter by activist investors for his lack of commitment. Elon Musk is worshipped by a massive audience who he tells he works hard, whilst simultaneously spending a load of time on twitter. It's performative.

Who is the company who went from 0 to 40 mill ARR in 9 months?
Long hours is just 'the old lie' in a business context... Dulce et Decorum Est
A meta rant - There's a lot of cancel culture at play around working hard.

I don't understand why people are trying to guilt/shame others into working less. And yet, at the same time, watch documentaries about successful people (Kanye, Michael Jordan) talking about how hard they used to work and celebrate it.

In order for you to be on the top of your field, you need to put in hours and hours of work. You'd have to sacrifice the so called 'life' part of the equation. If you don't want to do that - fine! We just don't share the same values and priorities. Just like how I shouldn't shame you for not working hard, you shouldn't shame me for working hard.

If I start a company, it's totally okay for me to only get employees who share this view. I'd boast about how hard I work and how much we accomplished. I'd let my employees do that. And I'd compensate them accordingly. If you think that's toxic, so be it. I feel the real shame is not realizing your full potential and falling short of your dreams.

A lot of people are forced to follow other people dreams or worse, ambitions.

You are right about dedication. If I look back it's insane the amount of time I have spent improving my skills, learning new things. I don't do it for the money although sometimes it pays good.

I respect people working hard to launch a company but I cannot respect the posturing or the backstabbing dressed as professionalism.

"Working hard" has been proven time and time again that doesn't work. Most of the success stories you heard of weren't because of hard work but because luck and connections. But don't worry work 16 hours a day and you will be the next bill gates in no time. bruhhahahahaha I still find it funny that there are so many people who think hard work pays off.
IMO in the average case hard work doesn’t move you forward, but in exceptional cases it is a huge game changer. It’s probably true for most people that putting in crazy hours is pointless, but I absolutely believe that if you’re in a position to tolerate the effects and reap the benefits of those extra hours, it absolutely can be worth the pain.
Luck? I don't believe in luck, I make luck.

Same thing with connections. Want to know why connections mattered in every job I have had, including my current one? Because I worked my ass off, did more than was asked of me, volunteered to do work outside of my immediate scope of work and most importantly made a point to always be on at least one cross-organizational or team outside my immediate work unit so I could actually be noticed by others. Yeah, you aren't going to be successful solely from "working" for 16 hours a day - what you do with those work hours matters too.

And you know what? It worked. The best jobs are the ones that come looking for you.

Another way to stand out? Become part of the internal expert network that exists within every organization. I ended up interacting with a lot of our contracting folks and I would always go out of my way to let them know I was available for "geek speak" translation - if they ever had something technical they didn't understand to just call me. Even if it wasn't for one of my contracts. Stuff like that provides dividends that can't be expressed by some silly metric. I'm pretty introverted but luckily those kinds of conversations tend to be one on one.

I find it beyond hilarious that there are so many people who think luck and "connections" are how most successful people got to where they are. Keep telling yourself that if you like and good luck with that long term. Success is not accidental and yes, good old fashioned (meaningful) hard work will still pay off.

This article resonated with me as I have worked in a toxic startup environment that required 70+ hour work weeks. That company checked every box in the 2nd list:

  - The market is not large enough right now. It was a huge market with huge incumbents with deep pockets
  - The product is bad. A poorly designed product written by junior engineers
  - Poor positioning. Fighting the big companies with no real value add is not a good strategy
  - High competition. See above.
  - Not talented team members. A rotating door of employees that leave in frustration.
  - Poor alignment. Constant down time and everything is always on fire (hence 70+ hour work weeks).
  - Poor founder. Definitely.
I still "work long hours" but not for the company. I enjoy technology and learning new things. I put in my regular hours for the companies I work for and my hobby is playing with other technology. I get to learn new things and my employers benefit. As an example, I learned kubernetes on the side. When the time came to build a new cloud platform, I was in a position to be the expert at it and was able to implement the platform for my employer, resulting in millions a year in cloud savings.