---
title: "Armin Ronacher: The True Shared Language of Software Projects Is Conceptual Understanding, and AI Agents May Break the Friction That Synchronizes Teams"
source: "Simon Willison 博客（Atom）"
source_tier: "t2"
url: "https://simonwillison.net/2026/Jul/14/armin-ronacher/#atom-everything"
permalink: "https://feed.astralor.com/items/itm_87fb36a4c3ad440e0b6dfbe3"
published: "2026-07-14T18:04:23.000Z"
score: 77
channel: "ai"
tags: ["AI Coding Agent","Armin Ronacher","Shared mental models","Software engineering collaboration"]
---

# Armin Ronacher: The True Shared Language of Software Projects Is Conceptual Understanding, and AI Agents May Break the Friction That Synchronizes Teams

## AI commentary

> This insight hits the neglected 'sociology of software engineering' amid the AI coding boom. It's a wake-up call for teams adopting AI-assisted coding. It's worth every tech lead pondering: are we sacrificing the foundation of long-term collaboration in pursuit of short-term efficiency?

## At a glance

In 'The Tower Keeps Rising,' Armin Ronacher argues that the shared language of a software project is not English or Python but a common understanding of concepts, boundaries, invariants, ownership, and system shape. This language lives in documentation, code, code review, conversations, and arguments. Before AI agents, friction — like reading others' code, asking questions, and coordinating — maintained this synchronization. While slow and seemingly wasteful, part of that friction is the process of transferring understanding and confirming consensus. AI agents may eliminate this valuable friction, leading to team fragmentation.

## Key points

- The true shared language of a software project is conceptual understanding, not a programming language.
- Friction (e.g., code review, conversations) is a key mechanism for synchronizing team understanding.
- AI agents may undermine consensus maintenance by eliminating this friction.

## Full text

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 was maintained by friction. 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. 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. — Armin Ronacher, The Tower Keeps Rising Tags: ai, software-engineering, llms, coding-agents, ai-assisted-programming, generative-ai, armin-ronacher, agentic-engineering

---

Verify against the original before citing; curated by Astral Feed: https://feed.astralor.com/items/itm_87fb36a4c3ad440e0b6dfbe3