3 ms·
If you already work for them for free, why should they pay you?
by charcircuit 4y ago
If you already work for them for free, why should they pay you?
- pengaru 4y ago> If you already work for them for free, why should they pay you? Because they'd like you to do it full-time instead of only in your spare time?
- charcircuit 4y agoBut why not hire someone else to do it full time so you have full time + part time.
- pengaru 4y agoBecause the part-time volunteer contributor has already demonstrated aptitude and interest in the project, they don't even need to be interviewed or trained. For large companies one of the obvious value-adds of OSS is it optimizes out the whole time-consuming, costly, and error-prone recruiting/hiring/training process. That all occurs voluntarily on the contributor's time who's so interested in the work they've already sought out the job, developed a rapport with the collaborators, and have been doing it for free.
- dyingkneepad 4y agoBecause then you'll have to do whatever is the priority that they think you should be doing, instead of doing whatever you previously wanted to do with it.
- iLoveOncall 4y agoThis is an extremely shortsighted comment. If they don't pay you they: - Have no incentive to make you continue contributing, - Have no decision power over what component you contribute to, - Have no decision power over when or how often you contribute, - Have no ground for asking that you follow any particular process (due to the first point), - etc.
- charcircuit 4y agoAll of these can be accomplished via social engineering instead of paying.
- ElevenLathe 4y agoThey have to pay somebody to do the social engineering too.
- humps 4y agoBecause they are under no obligation to continue contributing, and if the organization is serious about the future of the project and spot some talent, they'll want to try and get that person into a more permanent role. The real question is actually the opposite of the one you asked: why wouldn't they want to try and pay you for your work if it's beneficial to the product/company?
- bonzini 4y agoPlus you may not be working on exactly what they need from the project, but you already know the domain, the code base and the people. Even if they let you keep a few hours to do the stuff you were doing before, it's a net gain.
- quickthrower2 4y agoImagine you make $300 for every hour someone spends and you pay them $100. Crude, and you can disagree with the numbers, but this is the general idea when employing people. You get 4 hours a week for free, you make $1200 - $0 = $1200 You get 40 hours a week for $4000, you make $12000 - $4000 = $8000 By hiring them, you make more profit. You could try to get 10 people doing 4 hours a week for free, but maybe there is a limit to the number of people willing. Let alone the coordination and efficiency advantage of dedicating more time per week to tasks.
- cestith 4y agoYou also get to align their projects within your codebase to the rest of your efforts and strategic vision by way of paying them.
- charcircuit 4y agoYou can just talk with them to figure out something high impact that they would like to work on.
- cestith 4y agoYou can try. Let me know how that works out for you, especially when you need someone to fix a small niggling but uninteresting bug.
- charcircuit 4y agoPay another person to work 40 hours and now you make $9200 instead of $8000. By hiring them you are losing the work you would have gotten for free. As you said there is a limit for how many people are willing to work for free so you shouldn't get rid of the ones willing to work for free.
- peteforde 4y agoThis dumb question has an important answer: accountability and longevity. It's the same reason CIOs of large companies pay more to work with companies that provide a Service Level Agreement: their bosses (aka the board of directors) wants to know that there's someone smart who will pick up the phone if there's a real problem, 24/7. And someone to sue if things go south. If someone is making excellent OSS contributions to libraries that you rely on, it is legitimately unsane to not try hard to hire them. It means that they won't be recruited by someone smarter, distracting them from further contributions. Also, if you bring these folks into your culture, it's almost always a huge win/win because they are already up to speed without training. They are already true believers, and you're rewarding their early belief in your vision by unblocking them so that they have their needs covered, allowing them to be even more productive. You'd be hard pressed to find a more potent way to hire top talent. The idea that you are somehow getting ahead by not hiring someone who wants to be hired is probably the most expensive wrong idea you hold.
- em-bee 4y agocode ownership could also be a factor. if a contributor gets hired, their new code gets owned by the company
- aussiesnack 4y agoIf your question is a sincere one, then you're asking, of employees who have been approached by companies via OS contributions, "why did they do that when they could have got that work for free?". Hearing from employers who have done this might be interesting, but I'm not sure that the employee would be the right person to ask. On the face of it, however, to me at least it reads like your 'question' is less interesting: a rhetorical restatement of "companies don't do this". Then the 'evidence' you offer is an invented just-so story. Like all such stories it reflects your response to the world and the domain of your imagination, but tells us nothing about the world itself. It's a plain empirical fact that companies either do this, or they don't, and you find out which is the case by examining reality, not by weaving tales. Telling stories to assert that the world 'must' be as we perceive it is common but without worthwhile uses outside of debate halls.
- charcircuit 4y agoI am not offering any evidence for my position, but I am saying that not hiring seems like it could be a more optimal business move.
- aussiesnack 4y agoWhich is a very odd response to a question of fact. Rationalism 'ain't dead yet, it seems.