FWIW, I went from ~40/hrs week full-time programming to ~15/hrs week part-time programming after having a kid, and it’s not obvious to me that I get less total work done. Certainly not twice less. But I would never have said I worked hard, so I could have predicted as much.
I find this interesting but confusing. Do you have an idea for what mechanism allowed this? E.g: Are you getting more done per hour now than your best hours working full-time? Did the full-time hours fall off fast at a certain point? Was there only 15 hours a week of useful work for you to do and the rest was mostly padding?
Yes. I don’t think the argument requires that the work be hard (or that you work hard at it, whatever that really means). I believe it’s quite generally true that for most activities (howsoever achieved), productivity drops as hours spent increases. Then the rest of the argument follows.
FWIW, I went from ~40/hrs week full-time programming to ~15/hrs week part-time programming after having a kid, and it’s not obvious to me that I get less total work done. Certainly not twice less. But I would never have said I worked hard, so I could have predicted as much.
I find this interesting but confusing. Do you have an idea for what mechanism allowed this? E.g: Are you getting more done per hour now than your best hours working full-time? Did the full-time hours fall off fast at a certain point? Was there only 15 hours a week of useful work for you to do and the rest was mostly padding?
Yes. I don’t think the argument requires that the work be hard (or that you work hard at it, whatever that really means). I believe it’s quite generally true that for most activities (howsoever achieved), productivity drops as hours spent increases. Then the rest of the argument follows.