4 ms·

Curious how part-time those part-time developers have been, as well as what schedule/how much work the person you are replying to was looking for. I have succe

Curious how part-time those part-time developers have been, as well as what schedule/how much work the person you are replying to was looking for. I have successfully gotten 80% four-day-week at a string of engagements... but I work in the non-profit academic sector, and get paid quite a bit less than that $200K+ salary. I think a four-day-week, or even a three-day-week, makes a lot more sense than tha 4-hours-a-day 5-day-week the OP was suggesting. Because, yeah, one (or certainly two) meetings could pretty much blow a 4-hour-day. But at the 4-eight-hour-day schedule I've been doing, I feel like there is still plenty of time for meetings and overhead, and I am pretty confident I end up 95% as productive working a four-day 32 hours as I would be working 40 hours. I feel like it would still work pretty well at 3-eight-hour-days too. Below that -- or trying to work four-hour days instead of fewer eight-hour days, I could definitely see problems with "overhead" or lack of commitment.

datavirtue 5y ago
The meeting is part of the work. Code flies from my fingertips instantly. Figuring what to code is the painfully time consuming part. Developers barely code in the enterprise.
- jrochkind1 5y ago
  Of course the meeting is part of the work, I hope I didn't suggest otherwise! I can only speak from my experience working 80% time in several different jobs, in nonprofit/academic environments. As above. (I enjoy writing code, if writing code was "barely" part of the work I wouldn't still be here. It seems like it would be impossible to get anyone who was good at writing code in a development/engineering job where coding was barely part of the work! But I'm not sure what this has to do with the feasibility of less than full time work as an engineer/developer).
ZainRiz 5y ago
An alternate setup I've seen at (this was for a super, super experienced distinguished engineer (like a Google L9) who wanted to work part time) was to work full time one week and then take one week off

datavirtue 5y ago

The meeting is part of the work. Code flies from my fingertips instantly. Figuring what to code is the painfully time consuming part. Developers barely code in the enterprise.

jrochkind1 5y ago
Of course the meeting is part of the work, I hope I didn't suggest otherwise! I can only speak from my experience working 80% time in several different jobs, in nonprofit/academic environments. As above. (I enjoy writing code, if writing code was "barely" part of the work I wouldn't still be here. It seems like it would be impossible to get anyone who was good at writing code in a development/engineering job where coding was barely part of the work! But I'm not sure what this has to do with the feasibility of less than full time work as an engineer/developer).

ZainRiz 5y ago

An alternate setup I've seen at (this was for a super, super experienced distinguished engineer (like a Google L9) who wanted to work part time) was to work full time one week and then take one week off