3 ms·
> No, I was talking about contractors keeping ownership of the code, for example, that people are paying them to make under contract. Great in theory, rare in
by PragmaticPulp 5y ago
> No, I was talking about contractors keeping ownership of the code, for example, that people are paying them to make under contract.
Great in theory, rare in practice. Usually when someone reaches the point where the code they’re writing for a company is self-contained and re-usable by other companies, they’re building a product rather than writing code.
Not strictly an app, but it’s still a product that must be maintained, supported, and sold.
I’ve hired many contractors and contracting companies to build code, features, or even products over the years. I can’t imagine a scenario where I’d willingly give any of them a license to maintain ownership of what I’m paying them to write and, even worse, a license to resell it to companies that are likely to be my competitors.
- unishark 5y agoIt's not rare at all. Any field where the company or person paying for the code has absolutely no ability to do anything with it themselves anyway. And frankly people tend to keep and reuse their code anyway, but I prefer to be honest about it. Here's an example I did: fast linear algebra algorithms in C to run an algorithm on a customer's device. They wanted the high level algo working, not my matrix code. I used it in other stuff for a really long time. One doesn't need everyone in the world to unanimously agree to one's license terms. It's fine if you're repulsed by the idea. That's a important flag when considering potential customers.