Earlier quoted context omitted.
> So, one of the questions would be: does 20h/wk + 20h/wk = 40h/wk skills+involvement, ie. is it linear? Wouldn't 20h/wk jobs be limited to inherently part-time, low importance tasks--which means you got to have plenty of funds to staff for them in the 1st place? It would seem to me that 2 people working 20h/wk offers some significant advantages over one person working 40h/wk. Firstly, it allows for fail-over; when o…
> 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 also don't think it's necessarily true that two part-time people would be less skilled or less focussed on work. It's the very point of the original article that working fewer hours can increase the quality and focus of the work done during that shorter period.
I've worked with many talented and exceptional "family guys" (and family women) who were skilled and totally focussed during working hours. I haven't noticed a correlation between people's priorities outside working hours and ability to do good work.