3 ms·
"Being a cofounder requires at least 80 hours of work a week. If you aren’t ready to work those hours, don’t start a company. Period." How true is this? I know
by jrs235 14y ago
"Being a cofounder requires at least 80 hours of work a week. If you aren’t ready to work those hours, don’t start a company. Period."
How true is this? I know VCs certainly want everyone to think and believe it. But really, how true is it?
EDIT: That comes off a little too absolutist for me.
- bps4484 14y agoAt the end of the day each person can only speak to their experiences and the experiences of those they know who wouldn't exaggerate. That being said, from what I have seen, it's not true for most people, and is even counterproductive for most people.
- general_failure 14y agoA big chunk of most software is about component assembly. You use frameworks and libraries. Stitch things together and make things work. Contrary to what most people say, 80 hours a week is not abnormal or counter-productive. It is probably counter-productive like if you do that for 2 years. But for a week? 3 months? 6 months? For most people who really are interested in things, this is no problem. I can vouch for this personally. When I am interested in things, I can work on code for months and I don't even keep track of time. And all of my projects don't even involve money. Back to my first paragraph, super-duper-brain work can be very draining and I cannot imagine working 80 hours a week in that case. But for most pulp software (like I do - hack on node.js, Qt, WebKit, HTML5..) bring it on. I can easily do things at a stretch with no fall in productivity. In fact, I find it counter-productive if I don't work on these problems in a stretch since I lose context. (WebKit debugging anyone?)