How to Design a Good API and Why it Matters
The Java Collections architect distills decades of API design into a tight set of heuristics. Still the canonical reference on the subject.

Lexical Scanning in Go
Rob Pike walks through the lexer he built for Go's text/template package — a small masterclass in using state functions and channels to write a parser that reads like prose.

JavaScript: The Good Parts
Crockford's walkthrough of the language — its good parts, its bad parts, and the historical accidents that produced both.

Tech Talk: Linus Torvalds on git
Linus visits Google in 2007 to explain — bluntly — why distributed version control is the right model, why CVS and Subversion are not, and how git's data model falls out of that.

Unexpected Benefits of Going Local-First
Linear adopted local-first to make the app feel instant — and ended up with a team that ships faster than the architectures it replaced. Artman on what fell out of the decision.

Distributed Systems Are a UX Problem
Treat reframes consistency, latency, and partial failure as user-facing concerns — and shows what good distributed-system UX looks like.

Atomic Design
Brad Frost lays out the methodology that named atoms, molecules, organisms, templates, and pages — the vocabulary most modern design systems still borrow from.