Historically, working 24 hours a day (I include sleep because after a certain number of hours you even dream of code or your business) for 1 year typically accomplishes more than working 3 hours per day for 8 years. Or 1.5 hours per day for 16 years. There is just some kind of economy of scale. --------- EDIT: I got downvoted. Come up with whatever standard of productivity you want (ANY standard that you want) and ad…
Says who? I've not found this to be historically so at all in my own perception. Feel free to share some data.
Work for only 3 hours a day, but everyday
21–30 of 146 posts
Re: Work for only 3 hours a day, but everyday
#22How to pull this through when you are paid by the hour?
Re: Work for only 3 hours a day, but everyday
#23I agree with the author with some exceptions: when you are working as a contractor or freelancer for someone else's project maybe 3h/day is not acceptable. When you've got externally imposed deadlines 3h/day may not be sufficient. But i agree that working less than 8h/day could be really more productive. I also liked the "less stuck for coding" topic as "...it is sometimes hard to go bed without solving some unknown…
> When you've got externally imposed deadlines 3h/day may not be sufficient. Lots of deadlines companies and thus their employees face are externally imposed (often from their customer(s)).
Re: Work for only 3 hours a day, but everyday
#24Re: Work for only 3 hours a day, but everyday
#25So no going out for drinks where you might have a hangover the next day?
Re: Work for only 3 hours a day, but everyday
#26Earlier quoted context omitted.
On the topic of work environment: in one job I worked at, we had the Internet machines completely separated from the work machines. If you needed to check something you had to physically walk over to the Internet desk. Great for focussing on the task at hand without distraction, and considering carefully what information you need.
But then how do you copy and paste from Stack Overflow?
Re: Work for only 3 hours a day, but everyday
#27Re: Work for only 3 hours a day, but everyday
#28Historically, working 24 hours a day (I include sleep because after a certain number of hours you even dream of code or your business) for 1 year typically accomplishes more than working 3 hours per day for 8 years. Or 1.5 hours per day for 16 years. There is just some kind of economy of scale. --------- EDIT: I got downvoted. Come up with whatever standard of productivity you want (ANY standard that you want) and ad…
If you find that you're effective for every hour you work regardless how long you work for then you're very fortunate and exceptionally unusual.
Re: Work for only 3 hours a day, but everyday
#29If I told you that every car needed 8 gallons of gas to drive 100 miles, you'd point out I was wrong - so many different makes and models, not to mention variables from tire pressure to driving style. Yet for the potentially even more complex range that is different people, it amazes me that so much of the advice is didactic - we all need 8 hours sleep, 8 glasses of water, and 8 hours of work with breaks is optimal.…
Therefore, even though I appreciate that this isn't a solution for everyone, I don't think it's fair to say that this boils down to just a personal experience with no external value.
Re: Work for only 3 hours a day, but everyday
#30Earlier quoted context omitted.
> When you've got externally imposed deadlines 3h/day may not be sufficient. Lots of deadlines companies and thus their employees face are externally imposed (often from their customer(s)).
they are also often bullshit deadlines that users dont care about but gets a few brownie points for management.