Writing

Law for Software Developers

Ongoing knowledge base / learning series — not a completed book.

An ongoing knowledge base translating legal concepts into the language of software engineering.

Overview

Law for Software Developers is an open-source knowledge base, not a finished book. It documents legal ideas software developers should understand — using engineering analogies, architecture impact, and practical checklists. The curriculum and articles live on GitHub and will keep growing.

Problem

Developers regularly hit contracts, privacy, IP, and liability, but legal writing is rarely framed in terms engineers already use.

What I built

Each topic follows a Developer Translation Framework: what it is, why it exists, why a developer should care, real-world and software examples, architecture impact, common mistakes, and a checklist. Study notes and articles are added as I learn.

My contribution

  • Set up the repository structure, framework, and initial articles from legal study notes.

Technologies

  • Markdown
  • GitHub

Related writing

Law for Software Developers

Defending the Law

Notes on positivism, Radbruch and Hart, and what it means to defend private and public legality — written for builders.

Read on GitHub

Law for Software Developers

Five Reasons to Study Law

Why studying law trains transferable judgment — critical thinking, structured reasoning, and communication — including for software work.

Read on GitHub