What can be the right to own the code?

Question

Web development

After reading the article “Google is like Karl Marx and the Robin Hood of the Internet: why a company supports cybercommunism,” I thought.

Now I know two options for owning your own code:
1. Proprietary, you work for a company and everything goes to it. Those. the code is not yours.
2. Open source - if you discard the element of mysticism, you work either for free, or you are paid, but within the framework of some open source foundation, and again, the rights to the code are not yours, i.e. if you wrote code for Apache Jakarta and then you come to the bank and say I want to use the code that I wrote at the previous work, it’s not at all a fact that it will be possible to do this. In a sense, the code is again not yours, but belongs to the community.

Question
1. Does it happen somehow differently?
2. But it is generally necessary - it seems that we are somehow working.

Answer 1

I personally either don’t open all the code I write at all or open it under a suitable GNU license - as a result, everyone owes me and I can do whatever I want with my code.

Answer 2

I work in a company, the code does not belong to me, but I don’t worry - the head with ideas remains with me. And this is the main thing.

Answer 3

IMHO it is possible in another way: when you are, for example, freelancing. At the same time, state in the contract that the subject of the contract is not a code, but an exclusive license to use the product being developed, and the source code remains yours and you can use it in other projects.
However, I am a programmer and I could be wrong.

Answer 4

When developing the code, you negotiate with the customer the license under which the code will be released. There are many different licenses, open, closed, mixed and others. For every taste. You can even come up with your own license.

Answer 5

The options are slightly different.
If you work under a contract (freelance or an employment contract - it doesn’t really matter), then you are paid for the application being developed. And from the rights to this code, you only have inalienable rights (for example, to authorship), if the contract did not include, for example, the sale of a license, as described above. Or you voluntarily transfer the rights to this code to some organization (Apache, FSF, Eclipse etc).
In this case, the code license is set by the organization you work for. And the apache example falls into this category. Whether this license is proprietary or open - it doesn’t matter if the code is not yours, you can’t, for example, make dual licensing at will, etc.
If you write a library that you license as you wish (either propietary or foss), but do not sell it, but only license it and receive money for developing the wrapper / infrastructure / implementation, then you part only with the part that you owe by contract.