2 ms·
The problem is, for the most part, that the dev will only get paid to work on aspects that advances the employing corporation's interests. It really is just a
by ThrowawayR2 6y ago
The problem is, for the most part, that the dev will only get paid to work on aspects that advances the employing corporation's interests. It really is just a job.
- MaxBarraclough 6y ago> It really is just a job. I'm not seeing the problem with that. You'll never have full freedom to work on whatever you like and get paid for it. Seems to me the salaried job approach will give the developer less freedom compared to the patronage model, as you say, but it also has advantages. It introduces corporate/organisational resources, so you won't have to personally fund your test server, and hopefully there will be competent management, etc. In practice I imagine it means better job security too, and at the risk of being circular, it's just more likely to happen and to pay you properly. > the dev will only get paid to work on aspects that advances the employing corporation's interests True, but compared to the work just never happening, that's still a good thing. If you instead rely on patrons, you're still beholden to someone else's interests. This takes us back to my first point: you can never have total freedom to work on what you want, and get paid for it.