Are 10-11 Hour Programming Days Feasible?
drc37 writes "My current boss asked me what I thought of asking all employees to work 10-11 hour days until the company is profitable. He read something from Joel Spolsky that said the best way to get new customers is to add new features. Anyways, we are a startup with almost a year live. None of the employees have ownership/stock and all are salary. Salaries are at normal industry rates. What should I say to him when we talk about this again?"
Here, this link is all you need to know: http://archives.igda.org/articles/erobinson_crunch.php. It's a bit of a wall of text, but you can read the first part and then skip to the end, which contains this nugget:
Fun with Anagarams! LADS HOST, SHALT DOS. HAS DOLTS. AD SLOTHS, HATS SOLD. ASS HO, LTD.
Indeed. Studies have shown that the peak point for knowledge workers is something like 7.5 hours a day, 4 days a week, so going up from the standard 8 hours a day, 5 days a week (which we have Henry Ford to thank for - he carefully researched the optimum working time for assembly line workers) is already giving you diminishing returns.
The third hand is traditionally referred to as 'the gripping hand' in nerd circles.
"Who is the Journal of Quantum Physics going to believe?" --Stephen Hawking
That's a nice story, but the fact remains that working programmers 10 hours a day for more than a couple of weeks max (for a particularly nasty deadline, for example) is just plain counterproductive. There are many years of stastistics to back that up. I don't have them right at hand, but I am sure someone here does.
The statement that a happy and relaxed development team is more productive is still true.