A contrarian take on working long hours
allisonpickens.substack.com
A contrarian take on working long hours
1–10 of 127 posts
Re: A contrarian take on working long hours
#2Re: A contrarian take on working long hours
#3Re: A contrarian take on working long hours
#4I 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.
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.
Re: A contrarian take on working long hours
#5It's literally the mainstream view...
Re: A contrarian take on working long hours
#6I 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 ho…
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.
Re: A contrarian take on working long hours
#7Re: A contrarian take on working long hours
#8I 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.
Re: A contrarian take on working long hours
#9But 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.
Re: A contrarian take on working long hours
#10I 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.