Code ownership, contracts, and the work that outlives the project
Who owns what you wrote, what your contract actually assigned, and what to do with the repositories nobody opens any more.
-
IP clauses in software contracts
The four clauses that decide who owns delivered software, what each one does, and which wording to push back on.
-
How to archive a GitHub repository
How to archive a repository, what archiving preserves, and why deleting old code is worse than it looks.
-
Is software engineering dead?
What has actually changed in software engineering, which parts of the job are under pressure, and what the work turns into.
-
Will AI replace programmers?
Which part of programming is actually being automated, which part is not, and what that means for the job over the next decade.
-
Who owns the code you wrote for a client?
How ownership of client code is actually decided, which contract clauses move it, and what happens when nobody signed anything.
-
Work for hire vs license
What work for hire actually transfers, how a licence differs, and which one your contract really uses.
You have repos you will never open again.
Private, finished, owned by you, and doing nothing.
That is the code labs pay to license. Non-exclusively, so you keep it.