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

Bullshit. When you're piling long hours, you make many mistakes, and that's totally independent from your passion, interest of whatever. This is just being tired.

BTW in 1998 I've worked 100+ hours/week for a few months; it ended in the hospital. So I think I've seen that from the inside, too.

As a high level knowledge worker (CEO or CTO), I may "work" for long hours getting informed on the latest trends reading HN. I can be in the office, or in the shower, ir running in the woods thinking about my next product. Heck, I can even be working, golfing with an important customer. By this metric of course I work 120 hours a week (though I spend at most 40 hours a week in the office).

However when you're typing in code, or carefully assembling a car engine, if you work too much you'll simply make more errors. This has been verified many times. It's absolutely not debatable. If you want to believe it's not this way, you're deluding yourself, and that's not good, don't do that.



BTW in 1998 I've worked 100+ hours/week for a few months; it ended in the hospital.

Hell of a difference between spending 50 hours a week on the job and spending 100. Everything you've said in this thread is undeniably true at 100 hours/week. Almost nothing you've said in this thread is generally true at 50.




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

Search: