I am having basically a 3-4 hours workday and have had for a few years now.
As a freelancer doing most work remotely, I can easily set my schedule. I charge clients per day, and so far I have never had a complaint about being too slow or too unproductive. I seem to very often be more productive than "full-time" employees.
A few years ago I was almost depressed because I thought I was very bad at work ethics. Doing other things during the day, spending some days as little as one or two hours on the client's project. Then I realized that the days where I would force myself to work 8 or 9 hours on a project usually end up with me staring at the screen and doing useless or even counter-productive things for hours.
I then switched into accepting it. My quality of life improved, the quality of my work seemed to not have changed or even improved a bit (I spend more time improving myself actually, learning new things) and I managed to raise my rates. So technically, I raised my yearly productivity by halving my workday.
Obviously, that's not the case for all jobs, but for software developers, I think I am not alone in that case: I can be productive 3 or 4 hours per day. After that, I can convincingly pretend to be productive but with very low value and probably a toll on my productive time on the next day.
For sure- There is already a massive tech culture of working say 20-30 hours a week. Particularly in management and consulting. Its just that its kind of taboo to acknowledge it.
I am having basically a 3-4 hours workday and have had for a few years now.
As a freelancer doing most work remotely, I can easily set my schedule. I charge clients per day, and so far I have never had a complaint about being too slow or too unproductive. I seem to very often be more productive than "full-time" employees.
A few years ago I was almost depressed because I thought I was very bad at work ethics. Doing other things during the day, spending some days as little as one or two hours on the client's project. Then I realized that the days where I would force myself to work 8 or 9 hours on a project usually end up with me staring at the screen and doing useless or even counter-productive things for hours.
I then switched into accepting it. My quality of life improved, the quality of my work seemed to not have changed or even improved a bit (I spend more time improving myself actually, learning new things) and I managed to raise my rates. So technically, I raised my yearly productivity by halving my workday.
Obviously, that's not the case for all jobs, but for software developers, I think I am not alone in that case: I can be productive 3 or 4 hours per day. After that, I can convincingly pretend to be productive but with very low value and probably a toll on my productive time on the next day.