Earlier quoted context omitted.
> To use an incredibly bad analogy: It's like moving from a monolithic "big iron" server to a pair or farm of smaller ones. There are many advantages, but it means it's now a distributed system with all the problems that can bring. The thing is that, as you noted yourself, the analogy doesn't hold, for people are not AWS servers waiting for charge or failovers. If they chose to work 20h/wk, it's presumably to spend t…
I think the analogy holds for the case of employees not having the capacity to give extra hours due to other commitments. However, I totally agree that people aren't AWS servers, and the reason I felt the analogy was bad was that such a mechanistic view doesn't leave room for the multitude of positive, human ways of working around such problems. For example: if an employer asks a 20h/wk employee to work extra hours,…
To me, it depends on how you cut the hours, and to what extent. I'm all for working shorter days, eg. 6-8h, 4-5 days a week; however, the more you get close to half-time or below, the more difficult it becomes to stay fully focused and as motivated as a (more) full-time employee. This is admittedly less of a concern if the person uses their free-time on related projects (eg. writing open-source stuff).