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.
-
How to archive a GitHub repository
How to archive a GitHub repository or a branch, what archiving preserves, how it differs from git archive, and why deleting old code is worse.
-
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 make a GitHub repository private or public, and what that does not undo
How to make a GitHub repository private or public, what changes when you do, what does not, and why private from the start differs from private now.
-
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.
-
How to delete a GitHub repository, and what you lose when you do
The steps to delete a GitHub repository, what deletion actually removes, what survives anyway, and when archiving is the better call.
-
Should you squash commits? What your git history is actually worth
The engineering case for and against squashing commits, what commit history carries that a snapshot cannot, and why it is most of a repository's licensing value.
-
Is code copyrighted? Software copyright, explained
What copyright protects in software and what it does not, how it differs from patents and trade secrets, who the author is, and where a licence fits on top.
-
What is vibe coding, and who owns the code it produces?
What vibe coding means, why it works and where it fails, and the question nobody asks until it matters: who owns code a model wrote, and can it be licensed.
-
Work for hire agreements for software: the five clauses that matter
The five clauses a software work for hire agreement needs, with plain-language sample wording, what developers should push back on, and what clients actually need.
-
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 software engineers?
Which part of programming is actually being automated, which part is not, and what that means for the job over the next decade.
-
Work for hire vs license
What work for hire actually transfers, how a licence differs, and which one your contract really uses.
Earn $500+ on every repo you never open.
Private, finished, owned by you: $500+ each to AI labs.
Non-exclusive, so you keep the code and are paid again on every re-license.