131–140 of 306 posts
Earlier quoted context omitted.
I’ve always been able to successfully negotiate those IP ownership clauses. Usually without any hassle at all.
US person detected. Good luck negotiating any terms in Europe. Not happening.
Good luck negotiating that with a FANG, smaller companies won't give a damn (unless they have a dumb HR department who doesn't understand how hard hiring devs is)
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…
Yeah that 2nd point is that quite often people need "full time salary" so it is not that management somehow has backwards thinking. I have a friend that can really work 4 hours a day, but he is a special case where he does not have a family to upkeep and no mortgage. He is also a bit hard on the frugality. But finding such person is basically 1 in a million. If I post a job with 4h a day which amounts to 1/2 of a nor…
Earlier quoted context omitted.
As someone who's hired part-time developers off and on for years.... the issue is that they typically start out working the agreed-upon number of hours, then begin to work less & less over time. There's no feasible way to make someone work more hours remotely, and they're usually sharp enough to get partway into a project before flaking out so that it's difficult to just replace them- you'd have to hire an entirely n…
The other issue is flow. Flow is vital for execution, and distributing your attention amongst multiple projects means your flow breaks. Also part time devs might not commit to daily meetings, or being on call for downtime incidents.
"They want rockstars, but they themselves are not that." Yes, that problem. Zappos is a shoe store. Uber is a taxi company.
I wonder if hiring big teams is a status/ego thing. I’ve never been in that position, but I couldn’t imagine myself deciding that I need an Uber-scale development team to build a service like Uber. Just seems wasteful and like it’d be a nightmare to manage.
The chain of responsibility for that goes up to the investors who put millions in a company and pressured the founders to "SCALE FAST"
Earlier quoted context omitted.
Are you hiring them per/hour? Why not do a part time salary position? They are expected to spend an agreed number of hours per week (or maybe do it by the day) and the salary is proportional to that. If they want to change the hours then renegotiate time and salary.
I think the pool of developers who are not freelancers, are OK with part-time work, don't need more salary than you're paying them for part-time work (like they have a cheap lifestyle or are already well-off?), and won't continuously keep looking for more work is in practice just a very small number of people. Sure, there's some people that meet that description, but just not very many. There's a reason the labor mar…
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…
Yeah that 2nd point is that quite often people need "full time salary" so it is not that management somehow has backwards thinking. I have a friend that can really work 4 hours a day, but he is a special case where he does not have a family to upkeep and no mortgage. He is also a bit hard on the frugality. But finding such person is basically 1 in a million. If I post a job with 4h a day which amounts to 1/2 of a nor…
You can argue that half time engineers are more than half as productive as a full time engineer because as others have said full time engineers don't work a full 8 hours anyways. While theoretically that's true, as I originally posted, that's not what I've seen. Based on my anecdotal experience, half time engineers are less than half as productive as a full time engineer.
So from both a productivity and economic perspective, it hasn't made sense.
This I think explains a large part of why it feels like there’s a status quo inertia in the job market.
Earlier quoted context omitted.
> You lost me with "extra". What I'm talking about are core product team members, not freelancers. It was "extra paperwork associated with the extra staff". As in, adding X% more staff means X% more staff-related paperwork.
So don't hire so many people? I don't understand the problem. Why would they be hiring "extras" anyway? As backup?
The idea being that if everyone's part-time, you need more people to get the same work done relative to if everyone was full-time.
Earlier quoted context omitted.
> Part time work for developers would also help women who don’t want to work full time when they have small children. How about "parent" instead of "women"?
1. Tech has small percentage of women. The ridiculous under representation of female coders is widely recognized as a problem and something that should be fixed. There are programs for recruiting women into CS Majors. But the imbalance will remain when women have babies and are given only the choices of the third shift or leaving their careers. 2. Women who choose breastfeeding, which can be 3-4 hours a day total, ar…
Earlier quoted context omitted.
As someone who's hired part-time developers off and on for years.... the issue is that they typically start out working the agreed-upon number of hours, then begin to work less & less over time. There's no feasible way to make someone work more hours remotely, and they're usually sharp enough to get partway into a project before flaking out so that it's difficult to just replace them- you'd have to hire an entirely n…
The other issue is flow. Flow is vital for execution, and distributing your attention amongst multiple projects means your flow breaks. Also part time devs might not commit to daily meetings, or being on call for downtime incidents.
Daily meetings kill flow