Joel: Five Easy Ways to Fail (in a Software Project)

Re:Joel: Five Easy Ways to Fail (in a Software Project) by brianr on Thursday October 25, 2007 @12:44PM (#72561)

That seems a bit counterproductive to me--if you know it's going to take more than 40 hours, then why not at least try to make an estimate? If you think that your weeks' work is going to take between 50-70 hours, then budget 70 hours and be glad (or get ahead!) if you finish early.

That said, I can't imagine any startup getting far by working 40 hours a week. 80-100 is probably a minimum for a founder... it has to be your focus, not just your 'day job'.

[ Parent | on HN ]

Re:Joel: Five Easy Ways to Fail (in a Software Project) by olavk on Thursday October 25, 2007 @03:57PM (#72637)

I wonder if anyone have actually done the experiment? When you are doing a startup, you want to work as much as possible, however it might very well be that you would be just as productive if you worked just 40 hours.

[ Parent | on HN ]

Re:Joel: Five Easy Ways to Fail (in a Software Project) by ph0rque on Thursday October 25, 2007 @04:14PM (#72644)

I'd be very interested in seeing such a study. I think the answer lies in not just how hard you work, but how smart you work; i.e. monitoring your productivity and adjusting various factors (length of time, time of day, etc.) to maximize productivity.

[ Parent | on HN ]