Article · 2026-07-14 · 4 moments

Quoting Armin Ronacher

The shared language of a software project is not English or Python but it is the common understanding of what its concepts mean, where the boundaries are, which invariants matter, who owns what, and why the system has the shape it does. This language is rarely written down in one place. It lives partly in documentation and code, but also in code review, conversations, arguments, and the experience of having to explain a change to somebody else. Before agents, some of this shared understanding w ✦ AI generated

Read original ↗

GUEST Armin Ronacher HOST Simon Willison

Mechanism

Before agents, shared understanding between engineers was maintained largely by friction — needing to read someone else's code, ask them questions, and coordinate with dependent teams before making a change, which was slow.

Ronacher describes how the slow, effortful process of having to consult others before changing shared code once forced people's mental models to stay in sync.

transcript

Armin Ronacher: If I wanted to change your storage layer, I usually had to read your code, ask you questions, and perhaps coordinate with another team whose service depended on it. This was slow, and much of that slowness was waste but not all of it was.

extends · 1

Claim◆

Friction between engineers is not pure waste — it is the process by which one person's understanding of a system becomes shared with another, and by which both discover whether they still agree on how the system works; this friction synchronizes people.

Ronacher's core thesis: the slowness of pre-agent collaboration wasn't just overhead — it actively synchronized people's shared understanding, a function now at risk as coding agents remove that friction.

transcript

Armin Ronacher: Some of it was the process by which your understanding became mine, and by which both of us discovered whether we still agreed about how the system worked. This friction synchronizes people.

Definition◆

The real shared language of a software project isn't English or Python — it's the common understanding of what its concepts mean, where the boundaries are, which invariants matter, who owns what, and why the system has the shape it does.

Ronacher argues that a project's true shared language is the tacit, collective understanding engineers hold about the system, not the literal code or prose used to describe it.

transcript

Armin Ronacher: The shared language of a software project is not English or Python but it is the common understanding of what its concepts mean, where the boundaries are, which invariants matter, who owns what, and why the system has the shape it does.

explains mechanism · 3extends · 1supports · 1

Claim

This shared understanding is rarely written down in one place; it lives partly in documentation and code, but also in code review, conversations, arguments, and the experience of explaining a change to someone else.

The tacit knowledge underlying a codebase is scattered across formal artifacts and informal human interactions rather than codified in a single source.

transcript

Armin Ronacher: This language is rarely written down in one place. It lives partly in documentation and code, but also in code review, conversations, arguments, and the experience of having to explain a change to somebody else.

explains mechanism · 1

Highlight slides

The Real Shared Language of a Project✦ from: The real shared language of a software project isn't English or Python — it's the common understanding of what its concepts mean, where the boundaries are, which invariants matter, who owns what, and why the system has the shape it does.Friction Wasn't Just Overhead✦ from: Friction between engineers is not pure waste — it is the process by which one person's understanding of a system becomes shared with another, and by which both discover whether they still agree on how the system works; this friction synchronizes people.Tacit Knowledge Over Literal Code✦ from: The real shared language of a software project isn't English or Python — it's the common understanding of what its concepts mean, where the boundaries are, which invariants matter, who owns what, and why the system has the shape it does.Agents Remove the Friction✦ from: Friction between engineers is not pure waste — it is the process by which one person's understanding of a system becomes shared with another, and by which both discover whether they still agree on how the system works; this friction synchronizes people.

Related episodes

Video · Syntax

Do You Read The Code? ⟡ HTTP Gets a NEW Method ⟡ Codex Gets Sol Ultra ⌁ Syntax Weekly ⌁

→

Video · Syntax

The Workflow of the Future With Zed

→

Video · Syntax

LGTM, Ship It: The AI Code Review Problem

→