Mental Models for Systems Engineering

Software abstractions rarely exist in a vacuum. Operating systems, distributed platforms, and developer tooling constantly wrestle with universal constraints: interface explosion, identity mutability, trust boundaries, strategic incentives, and organizational complexity.

A mental model is an intuitive framework that allows engineers to reason about complex systems from first principles without drowning in raw implementation details.

This collection is organized into two foundational pillars:

1. Cross-Domain Isomorphisms: How computing mirrors battle-tested solutions from law, biology, economics, and physical logistics.
2. Empirical Laws & Design Philosophies: The hard-won axioms, heuristics, and maxims that govern real-world software evolution.

Pillar 1: Cross-Domain Isomorphisms

1. Everything Is a File: Corporate Personhood and Shipping Containers

How UNIX avoided an O(M * N) interface disaster by borrowing the exact same flattening trick used by Anglo-American corporate law (Corporate Personhood) and twentieth-century intermodal freight logistics (Shipping Containers).

2. Sandboxing and Nest Architectures: Cloud Hypervisor, Firecracker, and gVisor

Comparing microVM and sandbox design philosophies through bird nests and biological parasitism: from Cloud Hypervisor's modern standard house, to Firecracker's bare cliff ledge, to gVisor's ruthless cuckoo chick (brood parasitism) tricking applications inside KVM.

3. Handles vs. Names: File Descriptors, Paths, and Royal Cartouches

Why operating systems decouple hierarchical paths from integer file descriptors, mirroring how ancient civilizations distinguished easily chiseled public names from unforgeable royal signet rings—and how this saves modern software from Time-of-Check to Time-of-Use (TOCTOU) race conditions.

4. Game Theory and Strategic Systems

How strategic interaction models—Nash Equilibrium, the Prisoner's Dilemma, zero-sum dynamics, and mechanism design—govern BitTorrent unchoking, consensus protocol incentives, and distributed rate limiting.

Pillar 2: Empirical Laws & Design Philosophies

5. Empirical Laws of Software Engineering

The foundational laws of software systems: Conway's Law (architecture mirrors communication), Gall's Law (complex working systems must evolve from simple working systems), Postel's Robustness Principle (and the modern security paradox), the Law of Demeter, and Lampson's Hints.

6. Worse Is Better: The New Jersey vs. MIT Philosophies

Richard P. Gabriel’s classic exploration of why technically crude systems (Unix and C) with radically simple implementations consistently defeat theoretically perfect systems (Lisp Machines and Multics) in real-world survival.

7. The Unix Philosophy and the Zen of Software

Durable design ethos: McIlroy's pipeline axioms, The Cathedral vs. The Bazaar, Convention Over Configuration, Dan McKinley's "Choose Boring Technology", and the Zen of Python.

8. Software Licenses and Governance Models

Understanding the legal spectrum of open-source software: Permissive (MIT, BSD, Apache 2.0 with patent grants) vs. Copyleft (GPLv2, GPLv3, AGPLv3), and why Apple aggressively purged GPLv3 from its platforms.

9. Milestones in Computing History

A decadal retrospective tracing the cyclical ~10–15 year paradigm waves of computing: from 1930s Turing machines to modern Transformers and specialized silicon.

10. Maxims, Aphorisms, and Humor in Software Engineering

Curated wisdom on the four stages of developer progression, the virtue of deleting code, the perils of cleverness, Cargill’s 90-90 rule, and Turing's halting boundary.