Theo on Why Natural Language Does Not Belong in a Terminal

A brief argument that developers’ attachment to familiar terminals can shape how they imagine new interfaces.

TBTheo BrowneSpeaker · Ping Labs
Channel
Theo - t3․gg
Published
Jul 9, 2026
Video
0:18
Read
1 min
Original
English
Open on YouTube
Scroll to read and the video shrinks to the bottom-right corner. Captions follow your reading language.
Reading languageAvailable in 2 languages
You're reading the original English.
SUMMARY

In 30 seconds

Theo Browne argues that developers are in a skeuomorphic phase: they treat the terminal as an ideal interface because it is familiar. Although he loves terminals, he says natural language does not belong in one.

  1. 1A skeuomorphic phaseTheo says developers are leaning on a familiar interface when thinking about new ways to work.
  2. 2A beloved interfaceHe loves his terminal but does not consider it the ultimate interface.
  3. 3Natural languageHe argues that familiarity is why developers keep placing natural language in terminals.

Takeaways

  1. Theo thinks developers overestimate the terminal as an interface.
  2. He believes familiarity and affection help explain its continued appeal.
  3. He argues that natural language does not belong in a terminal.
FULL TEXT

Read the edited text by chapter

Transcript only
01

Familiarity and the terminal

Theo questions the terminal as an interface for natural language. He connects its appeal to developers’ habits and affection for it.

I think software developers are in a skeuomorphic phase. We act as though terminals are the ultimate interface, even though I do not think they are particularly good interfaces. I say that as someone who deeply loves my terminal.

Natural language has no place in a terminal, but we pretend it does because the terminal is familiar. It is what we are used to, what we love, and where we like to imagine ourselves when we think about coding.

More from this channel

5 slides38:47EN
Theo - t3․gg· Oct 28, 2026Theo’s Long-Running Agent Experiments: Verification, Compute and CostTheo Browne · Ping LabsA skateboard game and two compiler projects show how repeated checks and flexible compute can sustain agent work—and how expensive those loops can become.Coding agentsAgent engineeringAI cost & performance+2
5 slides36:07EN
Theo - t3․gg· Oct 27, 2026Theo on Token Costs, Coding Agents, and the Price of AI CapabilityTheo Browne · Ping LabsA viral estimate of Lauren's AI spending prompts a closer look at cache pricing, benchmarks, and the changing work of coding agents.AI cost & performanceCoding agentsInference+1
5 slides30:37EN
Theo - t3․gg· Oct 26, 2026Theo’s Three Skills for Reviewing and Shipping with Coding AgentsTheo Browne · Ping LabsHow sol-loop, full-send and full-stop encode review, verification and different levels of merge authority.Agent skillsCoding agentsCode review & verification+2
2 slides0:43EN
Theo - t3․gg· Oct 23, 2026Theo Distinguishes Security Vulnerabilities from Active AttacksTheo Browne · Ping LabsA short explanation of why disclosed software flaws and reported attacks are different kinds of security news.CybersecuritySoftware engineering
6 slides29:22EN
Theo - t3․gg· Oct 22, 2026Theo on Security Vulnerabilities, Stolen API Keys and AITheo Browne · Ping LabsA look at the gap between vulnerability disclosure and patching, and a speculative account of why stolen inference keys may be valuable.CybersecurityAI securitySoftware engineering+1
4 slides31:13EN
Theo - t3․gg· Oct 20, 2026Theo on Why Smarter Models Help More Than DevelopersTheo Browne · Ping LabsFrom game modifications to compiler experiments, Theo revisits his assumptions about who benefits from more capable AI.Coding agentsDeveloper productivityHuman-AI Collaboration+1