Read, redline, and write contracts you can defend. MSA structure, SOW scoping, IP assignment clauses (especially in software work — who owns what), NDA scope and duration, indemnification limits, governing law and dispute resolution choices, and how to handle Indian counterparties differently from US/EU counterparties.
Contracts are interface contracts, literally. An MSA is the type signature of the business relationship. An SOW is the implementation. An IP assignment clause is the license declaration. An indemnity is the exception specification. Same architectural discipline you already use for library APIs — clear types, narrow contracts, defensive nulls, named exceptions. The legal version is just less expressive syntactically.
The Schedule A carve-out is your Gemfile.lock for IP — explicitly listing what you're bringing in pre-existing so it doesn't get accidentally absorbed. Without it, the dependency graph of "what's mine vs what's the client's" gets murky fast.
This course unlocks once you've finished its prerequisite. Open prerequisite →
You are going to like this module more than you think you will, and I want to predict it explicitly so that when it happens you can notice it. Engineers tend to enter contract rea…
Every consulting engagement, every product partnership, every contractor relationship, every advisor handshake involves a contract — explicit or implicit. Engineers tend to either…
Approach: Essential
Approach: Important
Approach: Important
Approach: Reference
1. Build your contract template library: MSA (Indian), MSA (US), SOW, NDA, contractor agreement, work-for-hire-with-carve-outs, EULA, Privacy Policy. Each as .md or .docx with ann…
7 lessons. Read in order; spiral back when you need to. By the end you'll have used the core ideas twice — once on the abstract, once on something you'll meet at work next week.