Live data from Hacker News

Why not hire part-time developers?

aklos.substack.com

191–200 of 306 posts

Re: Why not hire part-time developers?

#191
post #156

Earlier quoted context omitted.

The way many people I've known seem to achieve flexibility is to accept a role somewhere relatively laid back, typically at a large but non-tech corporation. If they're coming from a much more intense environment and working remotely, it often requires only a couple of hours work a day to over perform, if that. It seems like it's almost impossible to get a role that's explicitly part time (as you've experienced) but…

How do you in advance if it's relatively laid back?

If you're explicitly looking for part time you're probably not looking to advance too.

It's kinda either/or

Re: Why not hire part-time developers?

#192
post #54

"They want rockstars, but they themselves are not that." Yes, that problem. Zappos is a shoe store. Uber is a taxi company.

I've been thinking this a lot recently. Go to Uber, you're working at a taxi company. Go work for Facebook- two choices, nothing you do matters, or you're selling perverts adverts. Go work for Google - you have no choice their entire company is built on a search engine that hasn't changed much in 20 years, but you'll feel real proud of those "various bug fixes" that Google Sheets got in its latest release. These comp…

Winner!!

Re: Why not hire part-time developers?

#193
post #118
post #10

I experienced this in the extreme recently. I'm a very experienced dev in a very in-demand field. Money is not a huge priority for me in my career. Flexibility is. I have a proven track record of success in part-time roles after converting to part time at my previous company (after 2 years of full-time, of course). I spent 3+ months trying to get part-time engagements, and was willing to consider both consulting and…

We’ve tried part time developers, but so far haven’t been able to do it successfully. The problem usually comes down to 2 things: 1) there is a constant amount of overhead that is always needed regardless of how long you work for in a week. Meetings and collaboration to figure out what to build, discuss issues etc. if these take up 10 hours a week a full time dev has 30 hours to do other things where as a half time d…

> Meetings and collaboration to figure out what to build, discuss issues etc

Remote-first, multi-time-zone companies simply don't do meetings. All communication is async and written down. Work gets done without a lot of hemming and hawing and meetings-with-no-agenda-to-talk-about-setting-an-agenda-for-a-future-meeting. It's much more efficient to come to a decision over 7 asynchronous back-and-forths, and people have the opportunity to do some research during the conversation so their decision is better informed. The whole Open Source world [when development is not done within a corporation] works this way.

I think the problem is corporations are obsessed with a definition of productivity as "the person is constantly productive". If you're not in a meeting, or have a ticket in progress, or are doing training, clearly you are just wasting time. You can't be allowed to just ruminate, or research, or play around with an idea, or talk to other teams. They'd rather you be writing code now that will be obsolete in 6 months and take a year to replace, rather than take 2 months to come up with a plan for your code that will take 3 months to write and last for 3 years. We rush into things because we have to have something to show for our work every day, and as a result the quality is poor, and that costs more in the long run.

Re: Why not hire part-time developers?

#194

Earlier quoted context omitted.

In Switzerland jobs are usually advertised in %, where 40h-45h/week is 100%. From that it is also usual to talk about 80% or 4/5days/week (and so on for other percentages).

Fascinating! I heard the Netherlands has a strong part-time job culture too.

I’ve worked anything from 24-32 hours a week in the Netherlands, but never 40.

Salaries (even full-time) are crap though.

Re: Why not hire part-time developers?

#195
post #118

Earlier quoted context omitted.

We’ve tried part time developers, but so far haven’t been able to do it successfully. The problem usually comes down to 2 things: 1) there is a constant amount of overhead that is always needed regardless of how long you work for in a week. Meetings and collaboration to figure out what to build, discuss issues etc. if these take up 10 hours a week a full time dev has 30 hours to do other things where as a half time d…

> Meetings and collaboration to figure out what to build, discuss issues etc. if these take up 10 hours a week [...] There's your problem.

What's the alternative? Have some PM+EM write a perfectly detailed spec for you to implement? That sounds like hell. I can't imagine spending all my time building something that I had no input on designing.

Re: Why not hire part-time developers?

#196
post #50
post #10

I experienced this in the extreme recently. I'm a very experienced dev in a very in-demand field. Money is not a huge priority for me in my career. Flexibility is. I have a proven track record of success in part-time roles after converting to part time at my previous company (after 2 years of full-time, of course). I spent 3+ months trying to get part-time engagements, and was willing to consider both consulting and…

If you think your job as an engineer is to write code, then sure -- part time makes sense. If you think your job as an engineer is to build a solution as a team, then one person hopping in and out of availability creates a hassle for an entire team. Can't have project meetings on Mon / Fri because X is never there. If a project with involvement by a part timer isn't done by eod Thursday, a fulltime person has 2 dead…

But this is great. If your company culture doesn’t depend on everyone always being there, it has a million benefits unrelated to productivity.

Working becomes so much more relaxing.

Re: Why not hire part-time developers?

#197
post #167

Earlier quoted context omitted.

> Meetings and collaboration to figure out what to build, discuss issues etc. if these take up 10 hours a week [...] There's your problem.

Why is this a problem? You can replace meeting time with time reading specs / requirement if you’d like. Point is you need some constant amount of time to understand the problem domain. If 2 people need to do that then that’s twice the time needed.

We run a 5-person dev team (1 designer, 2 technical founders, 1 dev full-time, +1 part-time dev) with 30 minutes of sync-time per week for non-founders. Our part-time dev can perfectly run with those specs thanks to our encouragement of daily documentation and written specs rather than waiting for a big meeting to ask and be asked questions.

Re: Why not hire part-time developers?

#198
post #118
post #10

I experienced this in the extreme recently. I'm a very experienced dev in a very in-demand field. Money is not a huge priority for me in my career. Flexibility is. I have a proven track record of success in part-time roles after converting to part time at my previous company (after 2 years of full-time, of course). I spent 3+ months trying to get part-time engagements, and was willing to consider both consulting and…

We’ve tried part time developers, but so far haven’t been able to do it successfully. The problem usually comes down to 2 things: 1) there is a constant amount of overhead that is always needed regardless of how long you work for in a week. Meetings and collaboration to figure out what to build, discuss issues etc. if these take up 10 hours a week a full time dev has 30 hours to do other things where as a half time d…

> they are doing either multiple part time jobs or a full time job + part time job

Have you considered older workers that are nearing retirement? They're probably looking to lean-out, and a part-time job could give them activity in their lives, while getting you someone who is highly experienced in getting things done. You wouldn't be paying benefits, but probably a higher hourly rate (for less than 40 hours) to compensate.

Or job sharing, where you bring on two part-time workers. My sister did this for many years - it gave her time to raise her children while being able to pay a nanny + daycare. She worked Mon-Wed, and her job partner worked Wed-Fri. The overlap allowed them to coordinate, and they were able to call and send texts to each other at other times.

Re: Why not hire part-time developers?

#199
post #195

Earlier quoted context omitted.

> Meetings and collaboration to figure out what to build, discuss issues etc. if these take up 10 hours a week [...] There's your problem.

What's the alternative? Have some PM+EM write a perfectly detailed spec for you to implement? That sounds like hell. I can't imagine spending all my time building something that I had no input on designing.

I mean, that's one direction. But we could also give the part-time engineer more autonomy so that they can quickly make decisions on their own. They'll still need to spend time talking to people, but they can figure out an effective way to do that based on context—which might start out with them spending more time during the week just talking to people, but will fall off quickly once they build an understanding of their domain and the external interfaces of whatever they're building.

If my experience is anything to go by, this sort of self-directed collaboration—think "design discussions" rather than "meetings" or "ceremonies"—will end up far more productive for everyone involved.

Re: Why not hire part-time developers?

#200
post #177

Earlier quoted context omitted.

Someone who's getting offered $300K+ for a full time job... Even 50% of that is already a full-time salary for many.

Not if you have a 2M mortgage

This sounds like a choice made by the person who chose to get the 2M mortgage, which is broadly speaking an outlier rather than average outcome.
Post reply on HN