An educational (not legal advice) guide to legal and intellectual-property basics for engineers and founders — why legal literacy matters (and when to get a lawyer), business entities (LLC/corporation, limited liability), the four IP types, copyright and software (code ownership, work-for-hire), patents/trademarks/trade secrets, software licensing and open source (permissive vs copyleft), contracts and agreements (NDAs, IP assignment, terms of service), and privacy/compliance (GDPR).
Legal issues have a way of being invisible right up until they're catastrophic — the open-source license you didn't read, the equity you didn't paper, the IP you didn't realize you'd signed away. Engineers and founders don't need to become lawyers, but a working literacy in a few legal basics prevents expensive, avoidable mistakes and tells you when you genuinely need professional help. This series builds that literacy. (An important note up front: this is general education, not legal advice — for real decisions, consult a real lawyer.)
Legal issues have a way of being invisible until they're catastrophic — the open-source license you didn't read, the equity you didn't paper, the IP you didn't realize you'd signed away. Engineers don't need to become lawyers, but a working literacy in a few legal basics prevents expensive mistakes and tells you when you need professional help. (Educational, not legal advice.)
The first legal decision most founders face is also one of the most consequential and least understood: what kind of legal entity is your business? The choice — sole proprietorship, LLC, corporation — determines whether your personal assets are shielded when things go wrong, how you're taxed, and whether you can raise money. Getting it right early is far easier than fixing it later. (As always: this is general education, not legal or tax advice — the specifics vary by jurisdiction and situation, so consult professionals for your case.)
The first legal decision most founders face is also one of the most consequential and least understood: what kind of legal entity is your business? The choice — sole proprietorship, LLC, corporation — determines whether your personal assets are shielded, how you're taxed, and whether you can raise money. (Educational, not legal/tax advice.)
Intellectual property is one of the most valuable assets a technology company has — and one of the most confused topics among engineers, who often use "copyright," "patent," and "trademark" interchangeably. They're not interchangeable: they protect entirely different things, in different ways, for different durations. Getting the mental map right — four distinct types, each for a different kind of creation — is the foundation for everything about IP. (As always: educational, not legal advice.)
Intellectual property is one of the most valuable assets a tech company has — and one of the most confused topics among engineers, who use 'copyright,' 'patent,' and 'trademark' interchangeably. They're not: they protect entirely different things, in different ways. Getting the mental map right is the foundation. (Educational, not legal advice.)
Every line of code you write is, the instant you write it, protected by copyright — automatically, with no registration required. That surprises many engineers, and its implications run deep: copyright is the legal foundation of who owns software, why you can't just copy others' code, and why software licenses (which grant permission around copyright) exist at all. Understanding copyright as it applies to code is the single most relevant piece of IP knowledge for a working engineer. (Educational, not legal advice.)
Every line of code you write is, the instant you write it, protected by copyright — automatically, no registration required. Its implications run deep: copyright is the legal foundation of who owns software, why you can't just copy others' code, and why licenses exist. It's the most relevant IP knowledge for a working engineer. (Educational, not legal advice.)
Copyright protects your code automatically, but the other three kinds of intellectual property protect entirely different things and work in entirely different ways — one guards inventions in exchange for public disclosure, one guards your brand name and logo, and one guards secrets simply by keeping them secret. Each has its own logic, cost, and strategic use, and knowing which protects what (and when each is worth pursuing) rounds out an engineer's IP literacy. (Educational, not legal advice.)
Copyright protects your code automatically, but the other three kinds of IP protect entirely different things in entirely different ways — one guards inventions for public disclosure, one guards your brand, one guards secrets by keeping them secret. Knowing which protects what rounds out an engineer's IP literacy. (Educational, not legal advice.)
Every engineer uses open-source software constantly, and almost none read the licenses — which is a quiet risk, because those licenses are legally binding terms that govern what you can and can't do with the code, including obligations that can affect your own product. The difference between a permissive license and a copyleft one can determine whether you can keep your code proprietary. Understanding software licensing, especially open source, is among the most practically important legal knowledge for a working engineer. (Educational, not legal advice.)
Every engineer uses open-source software constantly, and almost none read the licenses — a quiet risk, because those licenses are binding terms governing what you can do with the code. The difference between permissive and copyleft can determine whether you can keep your code proprietary. (Educational, not legal advice.)
Contracts run the business world — every deal, job, partnership, and service relationship rests on one — yet most people sign them without really understanding what they're agreeing to. For engineers and founders, a few contracts matter enormously: the employment agreement that may assign your IP, the NDA that binds your confidentiality, the customer contract that defines your obligations. Understanding what contracts are and what to look for turns signing from a blind act into an informed one. (Educational, not legal advice.)
Contracts run the business world — every deal, job, and partnership rests on one — yet most people sign them without really understanding what they're agreeing to. For engineers and founders, a few contracts matter enormously: the employment agreement that may assign your IP, the NDA, the customer contract. (Educational, not legal advice.)
Handling user data used to be a technical matter; now it's a legal one, with real regulations, real penalties, and real obligations that engineers build software to satisfy. Privacy and compliance have become part of the job — and, along with the rest of this series' legal basics, they lead to the single most important lesson: legal literacy exists to tell you when you're out of your depth and need a real lawyer. This closing post covers privacy, compliance, and that essential meta-skill. (Educational, not legal advice.)
Handling user data used to be a technical matter; now it's a legal one, with real regulations, penalties, and obligations. Privacy and compliance are part of the job — and they lead to the most important lesson: legal literacy exists to tell you when you're out of your depth and need a real lawyer. (Educational, not legal advice.)
This series is part of a larger body of work by Pratik Dhanave, an Agentic AI Architect writing about production AI systems, distributed systems, and cloud-native engineering. Explore all course series, browse every post, or find topics via the tag index.