4 ms·

I believe strongly in a sustainable pace. Software development isn't like brick-laying - you can't work more hours, past the breaking point, and expect to get m

I believe strongly in a sustainable pace. Software development isn't like brick-laying - you can't work more hours, past the breaking point, and expect to get marginal returns. Sure, you'll get some sloppiness and "bugs" in bricklaying, but likely nothing that can fundamentally ruin the project. Software developers working too much lead to negative returns as they add more bugs than they fix (or add features). And sleep-deprived coding has lead to more architectural "bite us in the ass" problems than any slightly faster feature output. That's why I have a cap at ~40 hrs/week. Don't work any more or I'll get mad. And I believe in the "Results Only Work Environment" (http://www.gorowe.com http://www.gorowe.com) - there is no clock; folks "working late" or "coming in early" have nowhere to hide. Only the people working at a sustainable pace and consistently delivering high-quality, working software are rewarded. And we're hiring: http://fundinggates.com/jobs http://fundinggates.com/jobs

lucian303 15y ago
Nicely put. Results matter, not hours. Most people have still not grasped this. And coding late, or even into the next day is kinda like driving without sleep: dangerous, illegal (in many states), and likely to lead to the shittiest code one ever writes.
lwat 15y ago
I know companies that throw everyone out of the office at 6pm sharp. No working from home allowed either. They seem to be doing just fine. Sometimes you have to force people to work reasonable hours or they'll just burn themselves out in a year or two.
radikalus 15y ago
I strongly advocate pace as well; I don't think it's THAT dependent however on hours/week. I prefer working longer hours when my pace is high and working less when I'm feeling not very effective.
adrianhoward 15y ago
you can't work more hours, past the breaking point, and expect to get marginal returns I find it a little depressing how difficult it can be to convince folk of this though - both employers and employees. Once team I was brought in to help was working silly hours, and I could very quickly see that it was having a terribly effect on productivity. You could just look at the stories that were being worked on at 9pm on a Friday night and guarantee that you'd be seeing them again the next week with a bug report attached. I managed to persuade everybody to start working more sensible hours. We collected stone cold facts from the history of the number of bug reports and complaints + stories done that this was more productive on every scale. And yet..... push back from management (who were very invested in the "startup's work 60 hours a week" mindset) and some of the developers (who had become locked into "hero developer" mode). Even ignoring the ethical argument (not saying that you should) it's just more productive to work that way.

lucian303 15y ago

Nicely put. Results matter, not hours. Most people have still not grasped this. And coding late, or even into the next day is kinda like driving without sleep: dangerous, illegal (in many states), and likely to lead to the shittiest code one ever writes.

lwat 15y ago

I know companies that throw everyone out of the office at 6pm sharp. No working from home allowed either. They seem to be doing just fine. Sometimes you have to force people to work reasonable hours or they'll just burn themselves out in a year or two.

radikalus 15y ago

I strongly advocate pace as well; I don't think it's THAT dependent however on hours/week. I prefer working longer hours when my pace is high and working less when I'm feeling not very effective.

adrianhoward 15y ago

you can't work more hours, past the breaking point, and expect to get marginal returns I find it a little depressing how difficult it can be to convince folk of this though - both employers and employees. Once team I was brought in to help was working silly hours, and I could very quickly see that it was having a terribly effect on productivity. You could just look at the stories that were being worked on at 9pm on a Friday night and guarantee that you'd be seeing them again the next week with a bug report attached. I managed to persuade everybody to start working more sensible hours. We collected stone cold facts from the history of the number of bug reports and complaints + stories done that this was more productive on every scale. And yet..... push back from management (who were very invested in the "startup's work 60 hours a week" mindset) and some of the developers (who had become locked into "hero developer" mode). Even ignoring the ethical argument (not saying that you should) it's just more productive to work that way.