4 ms·
I worked 4x10 a week. I can speak to the experience. At times early in my career I took breaks away from programming. The role wasn't as mentally engaging as
by fellowniusmonk 5y ago
I worked 4x10 a week. I can speak to the experience.
At times early in my career I took breaks away from programming.
The role wasn't as mentally engaging as programming and you could leave your brain at the door when you left each day.
It was amazing, I almost stayed there permanently, I wasn't enamored with the work but each week was true mental reset.
I think we have to divide roles that requires deep work from roles that don't.
Just like we have to separate butt in seat inbound sales roles from programming.
For programming type roles, 5x5or 4x8 would work better in my estimation depending on meeting workload.
- travisjungroth 5y ago> I think we have to divide roles that requires deep work from roles that don't. Very similar is the background mind vs not roles. Some people are great at completely separating their professional knowledge work time from the rest of their life. I am not. If a company pays for me to write software, they’re also getting my time in the bath tub thinking about software. This is different from when I was parking cars as a valet. I would never, ever take a “reduced hours” software job for this reason. A job that had 25 hours on the books would occupy a similar amount of my headspace to a normal full time job but probably expect to pay less. For how many employees seem to want it and what a deal it is under the right circumstances, I’m a little surprised more companies don’t offer reduced hours schedules for software. Maybe some adverse selection component.