Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

60 hours weeks aren't sustainable, but just look at teams during crunch weeks. They sure get a lot of work done.

Sometimes you've just got to put the hours and effort in to get the work done on time.

Now I quit very quickly after doing stupid hours a week. But I'd like to think the work produced was fine. Not that much different to a normal week. The work was all planned in detail, there weren't any big surprises, just lots of code to type in, lots of tests to write and run. I was just more tired.



How much of that extra work was because of the extra hours put in and how much was because people work harder when deadlines are close?


I was talking with a colleague the other day about "strategies for how to focus for 4 straight hours".

The one that works best for me is for the deadline to be 4 hours and 15 minutes away.


That's a popular adage: "I have a motivation problem until I have a time problem."




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: