3 ms·
My own experience is that above 50 hours you start destructing value, not creating some. Examples: writing code filled of bugs you have to fix later, getting u
by shin_lao 15y ago
My own experience is that above 50 hours you start destructing value, not creating some.
Examples: writing code filled of bugs you have to fix later, getting upset on a problem you cannot find a solution for while you could be resting, taking the wrong decision, being cranky, etc.
Agreed, sometimes you have to go beyond the limit, but it's not sustainable.
- chunkyslink 15y agoI only agree with you if you so the same work for those 50 hours. If you work for 80, but this is split between marketing, coding, networking and strategy then its not the same thing. When I'm feeling the pressure, I just switch to another role.
- shin_lao 15y agoI see what you mean, but 80 hours means more than 11 / day without any rest. Not sustainable. Try doing smaller weeks, you might be surprised by the result.
- chunkyslink 15y agoLike that idea, but I'm working a day job and then my business. Not sure I can !
- alnayyir 15y agoYour body and psyche don't care what sort of excuses or goals you have for it.
- tensor 15y agoYes, but networking and marketing is not even close to as taxing as coding or solving mathematical problems. This is so much the case, that I generally discount business dinners as not work.
- bedris 15y agoThat depends on your proclivities and the natural bent of your personality. Networking and marketing may not be as intellectually taxing as coding, but they can be physically and emotionally taxing when done in person for significant amounts of time. Of course, if you regard business dinners and networking as enjoyable, they won't seem as taxing!