News for hackers. Stuff that matters.
Re:Why not hire part-time developers? by wpietri on Sunday February 27, 2022 @06:31PM (#30493999)
As a developer, I agree there's a cultural issue, but think there are pragmatic issues.

I have done both part-time consulting and part-time contract development. Pure consulting (when one's output is advice) is doable part time, because you're not a blocker and generally don't have to keep up with the day to day.

But I would only do part-time contract development under pretty specific circumstances: 1) I'm the only dev on the project (or at least I know the other devs really well), 2) I am not on the critical path for anything urgent, 3) the organization can sustain an interest in the work (and therefore in paying me) despite it not being urgent.

For example, I knew somebody who needed a discrete service, a PDF form-filler, replaced. The old version was a pain operationally and I think it was built on EOLed tech in a language the team didn't know. That was a fine part-time project because the existing thing worked tolerably well; I was just cleaning up a mess that bothered them. I'd feel the same about, say, tech debt cleanup. Or quick, throwaway prototyping.

But in general, software is a team sport, a collective intellectual work that requires a high level of coordination between both devs and many others. I don't want to be part time on a team of well-meshed full-timers because the overhead of keeping track of the team's progress is fixed. I'd have to spend a notable percentage of my time keeping up, and I'll be adding to the coordination burden of the team despite not contributing as much, so my net ROI is lower. I'd hate it.

That said, I'd be interested to see a project that's, say, all 4-day-a-week people. Maybe even people who work 6 hours a day, 4 days a week. I could imagine that working pretty well while still being enough to keep stakeholders satisfied.

Re:Why not hire part-time developers? by hn_go_brrrrr on Sunday February 27, 2022 @07:21PM (#30494461)
Even your pragmatic issues have a strong cultural component. There are quite a few important projects that on my team that we could afford to have take 20% longer. It's more important they have a good result than they arrive as soon as possible. We also have some projects we need done ASAP, which would naturally fall to a full-timer.
Re:Why not hire part-time developers? by wpietri on Monday February 28, 2022 @10:20AM (#30500737)
That could be a cultural component. But from what I've seen, more often it's a business component. Software features should have a high ROI. The later you put something in production, the lower the return and the higher the investment. Further, the longer a team's cycle time is, the harder it is for the organization to learn.

And even for issues that are "cultural", I think one needs particular strategies for managing them. Stakeholders for the important projects that are being delayed will generally not be excited about that. And given that most companies have competitors, those stakeholders might have legitimate reason to want things to go 25% faster. So I'd be curious to see what strategies people have for solving the cultural problems.

Re:Why not hire part-time developers? by twblalock on Monday February 28, 2022 @12:13AM (#30496670)
So, it makes sense to hire part-time people when the timelines can slip and they aren't on the critical path? That's not a very good sales pitch.
Re:Why not hire part-time developers? by hn_go_brrrrr on Monday February 28, 2022 @12:44AM (#30496806)
I'm getting downvoted, but I really don't see the problem? Not all of our projects even have a timeline to slip.
Re:Why not hire part-time developers? by wpietri on Monday February 28, 2022 @07:19PM (#30507239)
I can believe they don't have explicit timelines. But I'd bet there are implicit ones. Or are you saying that if you just never do them, nobody will notice?