People · Vol. XII · 2026 The system builders, annotated 44 portraits

Volume XII — opening pages

The people behind
the systems.

Behind every protocol, structure, language, and tool on this site is a person who first thought of it. This is a short, deliberately incomplete portrait gallery — five wings, organised loosely by what they shaped.

I

The foundations.

Theorists who gave us the vocabulary of computation.

Claude Shannon

Mathematician at Bell Labs · MIT
Open profile →
Gave us

Information theory. The bit. Channel capacity. The proof that a digital signal can be transmitted over a noisy channel with arbitrarily small error if you stay below the channel capacity.

Story

A 1948 paper, a single thinker, an entire field. Shannon also juggled, rode unicycles down Bell Labs hallways, and built mechanical chess-playing machines and a coin-tossing robot. Famously private, almost reclusive in his later years.

"Information is the resolution of uncertainty."

Marginalia Could juggle while riding a unicycle. The combination is documented.

Alan Turing

Mathematician · Government Code & Cypher School · NPL · Manchester
Open profile →
Gave us

The Turing machine. Computability. The Turing test. The architectural model of the stored-program computer (ACE).

Story

His 1936 paper "On Computable Numbers" defined what computation IS. He spent the war breaking Enigma at Bletchley. Persecuted for being gay; pardoned posthumously in 2013.

"We can only see a short distance ahead, but we can see plenty there that needs to be done."

John von Neumann

Mathematician · Institute for Advanced Study · Manhattan Project
Open profile →
Gave us

The von Neumann architecture (program and data in the same memory). Game theory. Cellular automata. Self-replicating systems.

Story

Hungarian polymath who could compute 8-digit divisions in his head as a child. Worked on the EDVAC, the IAS machine, hydrogen bomb math, and von Neumann's ergodic theorem in the same week.

Edsger W. Dijkstra

Computer scientist · TU Eindhoven · UT Austin
Open profile →
Gave us

Dijkstra's algorithm (shortest path). The semaphore. Structured programming. The "GOTO considered harmful" letter.

Story

Dutch, opinionated, and unapologetically theoretical. Wrote his EWDs (Edsger W. Dijkstra notes) by hand in numbered, dated essays — over 1300 of them.

"Computer science is no more about computers than astronomy is about telescopes."

Donald Knuth

Stanford emeritus · author of The Art of Computer Programming
Open profile →
Gave us

TAOCP (still being written). Big-O notation as we use it. TeX (the typesetting system). Literate programming. MMIX. Knuth-Morris-Pratt.

Story

Started TAOCP in 1962. Stopped using email in 1990 to "stay focused". Pays $2.56 ("hexadecimal dollar") for any error found in his books. Plays the organ.

"Premature optimization is the root of all evil."

Marginalia Stopped using email in 1990 to "stay focused". Pays $2.56 — a hexadecimal dollar — for any error found in his books.

Leslie Lamport

Microsoft Research · ex-DEC SRC · 2013 Turing laureate
Open profile →
Gave us

Logical clocks. Byzantine generals. Paxos. TLA+. LaTeX (yes, that LaTeX).

Story

Wrote the foundational papers of distributed systems while also writing the typesetting macros every academic still uses. Calls Paxos "easy" — the field disagrees.

"A distributed system is one in which the failure of a computer you didn't even know existed can render your own computer unusable."

Marginalia Named Paxos after a fictional Greek island. The paper was rejected for being too unserious. He waited a decade and republished it.
II

Languages & runtimes.

The people who shaped how we write code.

Dennis Ritchie

Bell Labs · co-creator of C and Unix
Open profile →
Gave us

C, the language. Unix, with Ken Thompson. The K&R book.

Story

Quiet, modest, monumental. Died a week after Steve Jobs in 2011 — got a fraction of the obituary coverage despite C and Unix being load-bearing for everything Jobs ever shipped.

Ken Thompson

Bell Labs · Google · co-creator of Unix · co-creator of Go
Open profile →
Gave us

Unix (with Ritchie). The B language (precursor to C). Regular-expression engines. Endgame chess databases. Co-designed Go at Google in 2007.

Story

A career that spans the design of multiple foundational systems decades apart. Wrote his "Reflections on Trusting Trust" Turing Award lecture about a compiler self-reproducing a backdoor.

"When in doubt, use brute force."

Bjarne Stroustrup

Morgan Stanley · ex-Bell Labs · creator of C++
Open profile →
Gave us

C++. Generic programming. RAII (resource acquisition is initialisation). The argument that abstractions can be zero-cost.

Story

Designed C++ in 1979 because Simula was too slow and BCPL too low-level. Forty-five years later, the language still ships in every browser engine, game engine, and database.

Guido van Rossum

Microsoft · ex-Dropbox · ex-Google · creator of Python
Open profile →
Gave us

Python. The language is named after Monty Python, not the snake.

Story

Built Python over Christmas break in 1989. Stepped down as BDFL in 2018 after the walrus operator (PEP 572) debate burned him out. Returned to active dev at Microsoft on CPython performance.

Marginalia BDFL stood for "Benevolent Dictator For Life". The "for life" part was negotiable.

Anders Hejlsberg

Microsoft technical fellow · creator of Turbo Pascal, Delphi, C#, TypeScript
Open profile →
Gave us

Turbo Pascal (the speed of compilation that defined an era). Delphi. C#. TypeScript.

Story

A career of designing widely-used programming languages, decade after decade. TypeScript started as an internal Microsoft project in 2010; ten years later it was eating JavaScript's lunch.

Graydon Hoare

Independent · ex-Mozilla · creator of Rust
Open profile →
Gave us

Rust. Started it as a personal project in 2006; Mozilla picked it up in 2010; it's now in the Linux kernel, AWS Firecracker, Cloudflare workers, Zed, and a thousand other places.

Story

Mozilla colleagues realised Rust's significance before Graydon did. He has since worked on Swift and now writes thoughtful blog posts about programming-language design.

III

The web.

Builders of the protocols and systems most engineers touch daily.

Tim Berners-Lee

CERN · W3C · Inrupt · creator of the World Wide Web
Open profile →
Gave us

HTTP. HTML. URIs. The first browser (WorldWideWeb on a NeXTSTEP machine). The Web itself.

Story

A 1989 proposal at CERN, written on a NeXT cube under his desk. Refused to patent the Web. His father Conway Berners-Lee independently invented the binary search tree in 1960.

"The web is for everyone."

Vint Cerf

Google chief internet evangelist · co-creator of TCP/IP
Open profile →
Gave us

TCP/IP, with Bob Kahn. The protocols that hold the internet together.

Story

Cerf's 1974 paper with Kahn ("A Protocol for Packet Network Intercommunication") is the founding document of the modern internet. Hearing-impaired since birth; became a tireless advocate for accessibility.

Paul Mockapetris

Inventor of DNS · USC ISI
Open profile →
Gave us

DNS. RFC 882 and RFC 883 in 1983. The hierarchical name system that replaced HOSTS.TXT.

Story

Designed DNS to handle a network of "thousands or millions" of hosts at a time when ARPANET had ~300. The decision to push delegation to the leaves is why DNS still works at internet scale.

Brendan Eich

Brave Software · ex-Mozilla · creator of JavaScript
Open profile →
Gave us

JavaScript. Wrote the first version in 10 days in May 1995 for Netscape. Co-founded Mozilla; later founded Brave.

Story

JavaScript was supposed to be a "scripting language for designers" subordinate to Java. It became the most-deployed runtime on Earth.

Daniel Stenberg

wolfSSL · creator and maintainer of curl
Open profile →
Gave us

curl and libcurl. The HTTP client running in cars, refrigerators, satellites, every Linux distro.

Story

Started curl in 1996. Twenty-eight years of nights-and-weekends maintenance turned a personal utility into infrastructure on billions of devices. Famously responded to a corporate "we have a curl issue" email by listing the dollar amount his volunteer work was saving them.

David Karger

MIT professor · co-founder Akamai
Open profile →
Gave us

Consistent hashing (1997 thesis with collaborators). The Akamai CDN.

Story

Karger's consistent-hashing paper was originally about CDN load distribution. Today the same idea is in every distributed cache, KV store, and shard router.

IV

Data & databases.

The people who taught us how to store things.

Michael Stonebraker

MIT · creator of Ingres, Postgres, Vertica, VoltDB · 2014 Turing laureate
Open profile →
Gave us

Postgres. Ingres before that. Vertica, VoltDB, Tamr after. The argument that "one size doesn't fit all" in database design.

Story

A career of starting database companies, selling them, and starting the next one. The Postgres lineage powers every modern relational + extension story (CockroachDB, Citus, TimescaleDB).

Jim Gray

Microsoft Research · ex-Tandem · 1998 Turing laureate
Open profile →
Gave us

Transactions, granularity of locks, ACID. The idea that databases should be measurable (TPC benchmarks).

Story

Lost at sea in 2007, single-handed sailing trip from San Francisco. The CS community ran a search-and-rescue operation using satellite imagery and crowd-sourced volunteers; he was never found. The 2009 book "The Fourth Paradigm" was assembled in his memory.

Rudolf Bayer

TU München emeritus · Boeing Research
Open profile →
Gave us

B-trees (1971, with Edward McCreight). Red-black trees (1972, "symmetric binary B-trees"). Most of how indexes work, full stop.

Story

Designed B-trees while working at Boeing's research labs. Refused to commit to what the "B" stood for — Bayer? Balanced? Boeing? Broad?

Marginalia The B in B-tree is officially "the letter that comes after A-tree". This is the canonical answer.

Pat Helland

AWS · ex-Microsoft · ex-Salesforce
Open profile →
Gave us

Decades of architecture papers — "Life Beyond Distributed Transactions", "Immutability Changes Everything", "Identity by Any Other Name". The thinker behind a generation of distributed-database designs.

Story

Worked on Tandem, then SQL Server, then BigTable-era Google, then Salesforce, now AWS. Each paper is short, sharp, and quotable. His "Memories, Guesses, and Apologies" piece is the canonical framework for thinking about eventual consistency.

Martin Kleppmann

University of Cambridge · author of Designing Data-Intensive Applications
Open profile →
Gave us

DDIA (the book). CRDT research. The Hermitage tests for database isolation levels.

Story

A working engineer turned researcher who can write for both audiences. DDIA is the most-recommended technical book of the 2020s. Now researching local-first software at Cambridge.

V

Craft & community.

People who shaped the practice, not just the technology.

Brian Kernighan

Princeton · ex-Bell Labs
Open profile →
Gave us

AWK (the K). The K&R book. "The Practice of Programming". "The Go Programming Language" (with Donovan).

Story

The clearest technical writer in the history of computing. Co-wrote books with Ritchie, Pike, Donovan, Plauger. Coined "Hello, World!" — sort of; the phrase predates him but K&R made it canonical.

Linus Torvalds

Linux Foundation fellow · creator of Linux and Git
Open profile →
Gave us

Linux (1991). Git (2005, written in 10 days because BitKeeper revoked Linux's license).

Story

Two pieces of infrastructure that hold up most of computing — both written as personal projects. Famously direct on the kernel mailing list; mellowed considerably after a 2018 self-imposed sabbatical.

Marginalia Wrote Git in ten days. Named it after himself ("git" being British slang for an unpleasant person).

Margaret Hamilton

Hamilton Technologies · ex-MIT Instrumentation Lab
Open profile →
Gave us

The Apollo flight software. Coined the term "software engineering". Foundational work on fault-tolerance and priority scheduling — used to recover Apollo 11's landing computer when alarms went off seconds before touchdown.

Story

Photographed standing next to a stack of Apollo source-code printouts taller than she was. The image is the most-shared piece of programming history on the internet.

"I fought to bring the software legitimacy so that it — and those building it — would be given its due respect."

Grace Hopper

US Navy Rear Admiral · creator of the first compiler
Open profile →
Gave us

A-0, the first compiler (1952). FLOW-MATIC, which became COBOL. The argument that programming languages should be human-readable.

Story

Joined the Navy at 37, retired at 79 (the Navy kept calling her back). Carried "nanoseconds" — 11.8-inch lengths of wire — to demonstrate the distance light travels in a billionth of a second. Found the original "computer bug" — a literal moth in the Mark II.

Marginalia The moth, taped into a logbook with the note "first actual case of bug being found", is in the Smithsonian.

Barbara Liskov

MIT · 2008 Turing laureate
Open profile →
Gave us

CLU (the first language with abstract data types). The Liskov substitution principle. Distributed-systems work on Argus and Thor.

Story

First American woman to earn a PhD in computer science (Stanford 1968). Her LSP — "if S is a subtype of T, then objects of T may be replaced with objects of S without altering correctness" — is one of the few principles every working OO programmer can name.

Dan Luu

Independent · ex-MS · ex-Centaur · prolific essayist
Open profile →
Gave us

A library of widely-cited engineering essays — on processor design, latency, hiring, "computer latency: 1977-2017", "the empirical case against branch prediction performance papers".

Story

A working hardware engineer who blogs at danluu.com and quietly changed how a generation of engineers think about benchmarking, hiring, and "what does the data actually say?".

Joe Armstrong

Ericsson · co-creator of Erlang
Open profile →
Gave us

Erlang and OTP (1986). The "let it crash" philosophy of fault tolerance. Process supervision trees that have run telecom switches for decades at nine-nines availability.

Story

Designed Erlang to keep AXD301 phone switches running through hardware faults, software bugs, and live upgrades. The patterns he formalised — supervisors, GenServers, hot code reload — show up in every modern actor framework, from Akka to Elixir.

Ada Lovelace

Mathematician · the first programmer
Open profile →
Gave us

The first algorithm intended for execution on a machine — a Bernoulli-number computation for Babbage's Analytical Engine, written in 1843.

Story

In annotated notes on a French paper about the Analytical Engine, Lovelace went well beyond the source: she described conditional branching, loops, and the machine's potential for non-numeric computation ("composing music"). The Engine was never built; her algorithm is older than electricity-powered computing by a century.

VI

Distributed-systems pioneers.

They named the patterns that named the field.

Eric Brewer

UC Berkeley · ex-Google VP · CAP theorem
Open profile →
Gave us

The CAP theorem (2000 keynote, formalised by Gilbert & Lynch in 2002). Founded Inktomi (early search engine). Engineering leadership for Google's infrastructure, including the Bigtable / Spanner lineage.

Story

Brewer's "Towards Robust Distributed Systems" PODC talk introduced the CAP trilemma — pick any two of consistency, availability, partition tolerance. The later 12-years-later retrospective ("CAP Twelve Years Later") is a more nuanced version of the original claim and required reading.

Pat Helland

Tandem · Microsoft · Amazon · Salesforce
Open profile →
Gave us

"Life Beyond Distributed Transactions" (2007), "Idempotence Is Not a Medical Condition" (2012), "Building on Quicksand" (2009). The most quotable systems essayist of his generation.

Story

Worked on every major distributed database of the last 40 years. His essays about why exactly-once delivery doesn't exist, why conflict resolution must be application-specific, and why "eventual consistency" needs better marketing are still cited in design docs at every company you've heard of.

Werner Vogels

CTO of Amazon · Dynamo paper
Open profile →
Gave us

Co-author of the Dynamo paper (2007). The "everything fails, all the time" engineering culture at AWS. The All Things Distributed blog, where AWS's architectural decisions are explained in long form.

Story

Took the principles from his PhD work at Cornell on highly-available distributed systems and turned them into AWS's operational doctrine. The blog post "Eventually Consistent" (2008) is the canonical introduction to that consistency model.

Brendan Gregg

Intel · ex-Netflix · ex-Joyent · performance engineer
Open profile →
Gave us

The flame graph (2011) — now the standard CPU-profiling visualisation. The USE method (Utilisation, Saturation, Errors). The DTrace and BPF performance toolsets.

Story

A Netflix performance engineer who turned arcane kernel introspection into a craft anyone could practise. His book "Systems Performance" is the practitioner's reference. Flame graphs alone changed how an entire industry profiles software.

Adrian Cockcroft

Sun · Netflix · AWS · serverless evangelist
Open profile →
Gave us

Engineered Netflix's migration from a monolith to AWS microservices. Created and open-sourced the Simian Army (Chaos Monkey + friends). Defined the operational template every cloud migration since has copied.

Story

When Cockcroft joined Netflix in 2007, the company ran in a single data centre. Within five years it ran in AWS at multi-region scale, with a fault-injection testing culture that became the default for every large engineering org.

Marginalia Has personally migrated approximately one entire Netflix to AWS, give or take.
VII

Modern builders.

Engineers who shipped the load-bearing systems of the last twenty years — and somehow still answer GitHub issues.

Solomon Hykes

Co-founder of Docker · now Dagger · ex-dotCloud
Open profile →
Gave us

Docker (2013). Took kernel features that had existed for years (cgroups, namespaces, union mounts) and wrapped them in a Dockerfile and a CLI normal humans could use. Containerised the industry in roughly 18 months.

Story

Demoed Docker for the first time at PyCon 2013 in a five-minute lightning talk. The talk now has its own folklore status; many engineers remember exactly where they were when they first ran "docker run". Left Docker Inc. in 2018, building Dagger now.

"The best thing about containers is that you can run them anywhere. The worst thing is that you have to."

Marginalia Reportedly answers "what is a container?" with a five-minute philosophy lecture, then a one-liner.

Joe Beda · Brendan Burns · Craig McLuckie

Co-creators of Kubernetes at Google · Heptio · VMware · Microsoft
Open profile →
Gave us

Kubernetes (2014). Took everything Google had learned about Borg over a decade, redesigned it to be open-source, declarative, and CRD-extensible, and gave it away. Re-shaped what "infrastructure" means at most engineering orgs.

Story

Three engineers at Google in 2013, an internal pitch deck called "Project 7" (after Star Trek's Seven of Nine — the friendliest Borg), and a bet that the industry would eventually want this. Open-sourced 1.0 in 2015. By 2020 it was the second-largest open-source project on Earth.

Marginalia The codename was a Star Trek reference. It still is.

Salvatore Sanfilippo (antirez)

Independent · Redis Ltd. (until 2020) · now back to Redis
Open profile →
Gave us

Redis (2009). The argument that a single-threaded in-memory data structure server, written in C, would beat sharded clusters at most things people actually wanted from a key-value store. He was right.

Story

Wrote Redis in his spare time to power a real-time analytics product nobody used. Open-sourced it because the analytics product wasn't working. Stepped down in 2020 to focus on writing fiction; came back to Redis in 2024 because no one else was going to keep adding the data types.

"Programming is the closest thing we have to magic. Don't ruin it with too many threads."

Marginalia Writes science fiction in his off-hours and once published a Game-of-Life implementation in 700 bytes for fun.

Doug Cutting

Cloudera (chief architect) · ex-Yahoo · co-creator of Hadoop · Lucene · Nutch
Open profile →
Gave us

Lucene (1999, search). Nutch (2002, web crawler). Hadoop (2006, with Mike Cafarella) — an open-source clone of Google's GFS + MapReduce papers that powered a decade of "big data" infrastructure.

Story

Read Google's 2003 GFS paper and the 2004 MapReduce paper, then proceeded to spend the next two years implementing them in his garage office, named the project after his son's stuffed elephant. The name has outlasted the technology.

Marginalia The elephant is real. Was named Hadoop. Is presumably still around somewhere.

Jeff Dean · Sanjay Ghemawat

Google senior fellows · co-authors of MapReduce, Bigtable, Spanner, TPU
Open profile →
Gave us

MapReduce (2004), Bigtable (2006), Spanner (2012), the TPU. The pair-programming partnership that built most of Google's internal infrastructure and, by extension, the playbook for "hyperscale".

Story

They share an office and write papers together; the joke at Google is that they share a brain. The "Jeff Dean facts" meme — "Jeff Dean compiles and runs his code before submitting, but only to check for compiler bugs" — exists because the underlying productivity is unreasonable.

"— "Jeff once shifted a bit so hard, it ended up in another timezone.""

Marginalia There is an entire fan-website of Jeff Dean facts. Sanjay's contribution is doing all the work the facts skip over.

Ryan Dahl

Creator of Node.js · creator of Deno · independent
Open profile →
Gave us

Node.js (2009) — JavaScript on the server with non-blocking I/O. Deno (2018) — Node.js with all the things he wished he'd done differently the first time.

Story

Built Node in a few months in 2009 because nginx + JavaScript should have been a thing. Stepped away in 2012, came back in 2018 with a JSConf EU talk titled "10 Things I Regret About Node.js", then shipped Deno. Rare rebooter who didn't fork his own community.

"I think Node.js is the wrong abstraction. Maybe Deno is too. We'll see."

Marginalia The only language designer who has publicly listed his own regrets in a 30-minute conference talk.

Moxie Marlinspike

Founder of Signal · cryptographer · former sailor
Open profile →
Gave us

The Signal Protocol — X3DH key exchange, the Double Ratchet algorithm, sealed sender, prekey bundles. The crypto layer underneath Signal, WhatsApp, Skype, and Google Messages. End-to-end encryption for several billion humans.

Story

Lived on a sailboat for several years while building Signal. Rejected the idea of decentralisation for messaging — wrote a viral 2022 essay arguing centralised services are the only way to ship usable crypto. Stepped down as Signal CEO in 2022 but stayed on the board.

"Decentralised systems can move slowly because nobody is in charge. That is also their problem."

Marginalia Has a music album. Has lived on a boat. Has shipped end-to-end crypto used by half of humanity. Choose your hyphenated identity.

Geoffrey Hinton · Yann LeCun · Yoshua Bengio

2018 Turing laureates · the deep-learning trio
Open profile →
Gave us

Backpropagation in practice (Hinton, 1986). Convolutional neural networks (LeCun, 1989). Modern deep learning, AlexNet (with Krizhevsky and Sutskever, 2012), the architectures that became GPT and everything after.

Story

Spent thirty years working on neural networks while the field considered them dead. Got the last laugh in 2012 when AlexNet won ImageNet by a margin so large the field instantly pivoted. Hinton resigned from Google in 2023 to "speak freely" about AI risk; LeCun runs Meta AI; Bengio runs Mila in Montréal.

""We were the only people studying neural nets, because everyone else thought they didn't work." — Hinton, on the 1990s."

Marginalia Three of them. One of them — Hinton — credits his stubbornness to "being descended from George Boole, on his mother's side". (He is.)
Adjacent

From people, to their work.

Most of these names appear elsewhere on the site — in Papers, in Data Structures, in the guides themselves. This page is the index of the people; the rest is the index of what they made.

House rules

Reading-room conduct.

  1. § 1No flash photography. The portraits will not turn out anyway — none of these people sat for one.
  2. § 2You may attribute a quote, but you may not make one up. Lamport already did, and is still annoyed about it.
  3. § 3If you recognise yourself on this page, please email us a correction and a better quote. We pay $2.56 per error, hexadecimal.
  4. § 4The gallery is open 24 hours. The curator is asleep.
  5. § 5This museum is deliberately incomplete. The omissions are also a position.
Curated by Semicolony, anonymously · Plate XII · Volume 2026 · 44 portraits and counting
Found this useful?