3 ms·
I think the question isn't whether someone can code but whether someone is willing to work eighteen hours days. Even if someone could turn out more good code i
by joe_the_user 14y ago
I think the question isn't whether someone can code but whether someone is willing to work eighteen hours days.
Even if someone could turn out more good code in eight hours than the rest of the team turns out working eighteen hours, well not being around makes it harder to be part of the team.
But I'd say this is more of a testament to companies and standard practices which are more oriented to working people to burn out and throwing them away. That's not an efficient use of people certainly and it may not be an efficient use of the people's time. But it might just be an efficient use of the investors' money.
In ways, I'd say perhaps the young-guns might see that hiring old-farts could be a way to put a break umpteen-hour-weeks and so prevent the operation from having a burn-out-and-throw-away quality.
- EliRivers 14y agoI've been a programmer for more than a decade and 18 hour days are few and far between. This bizarre obsession with long hours seems to be common in a very small segment of the programming industry.
- eshvk 14y agoOddly enough, I see quite a few startups where this is prevalent and even celebrated. I remember talking to a YC company where top-down from the CEO, I was told that everyone worked 80+ hours a week and people were proud of the fact that occasionally they slept under their table. Looking closer at the operation (I spent a good few hours at their work place), It seemed apparent that most people were around late in the nights not because they were doing focused work for 18 hours but because they were inefficient enough that a significant bit of time was being spent doing other meta-non work related stuff. I suspect one of the reasons for this was that their "open office" environment was so incredibly distracting that there was so much context switching going on.
- pmjordan 14y agoI'm not really sure what point you're trying to make here. I completely fail see the logic behind 40-hour days making it hard to be a team player. I have to say most of the time as a programmer I'm staring at a screen on my own, even when I worked on a projects with 50 people. But then I've never been someone who was capable of being productive on 18-hour days. Even at LAN parties, when I was 16, I used to be the first one to go and catch some sleep. Still, having worked in the games industry, I'm no stranger to 12-hour workdays, and communication (face-to-face or otherwise) has never been anywhere near the bottleneck for me there. On the contrary, I used to get the most done in the quiet 1-2 hours before everyone else turned up. As far as I'm concerned, it's one thing for the founders of a company to put in a lot of hours, but I'd never work for another company expecting employees to do so beyond a reasonable extent (i.e. only when truly urgent).