Theo on Working Without Opening a Terminal

A reboot helped Theo realize that a more readable, organized interface had changed his coding workflow.

TBTheo BrowneIntervenant · Ping Labs
Chaîne
Theo - t3․gg
Publié
18 août 2026
Vidéo
0:28
Lecture
1 min
Diapositives
1
Original
anglais
Ouvrir sur YouTube
En faisant défiler, la vidéo se réduit en bas à droite et continue. Les sous-titres suivent votre langue de lecture.
Langue de lectureDisponible en 2 langues
Cet article n’est pas encore disponible en français ; il s’affiche dans l’original en anglais.
RÉSUMÉ

En 30 secondes

Theo Browne describes looking for a terminal he had not opened since restarting his computer. He says a readable interface, easier navigation and project organization encouraged him to code more.

  1. 1A changed habitTheo says he no longer does his work in a terminal.
  2. 2The missing terminalAfter a reboot, he searched for his terminal and realized he had never opened it because he had not needed it.
  3. 3Interface and organizationHe credits readable text, easy navigation and project organization with helping him code more.

À retenir

  1. Theo realized he had completed work without reopening his terminal after a reboot.
  2. He values readable text and easier navigation in a graphical interface.
  3. A category system and projects organized by local location helped him work more.
TEXTE INTÉGRAL

Lire le texte remanié, chapitre par chapitre

Transcription seule
01

Realizing the workflow had changed

Theo recounts a moment when he searched for an unopened terminal. He explains the interface features that made working easier for him.

I am not doing my work in a terminal anymore. A few days ago I was getting a lot done and used Command-Tab to look for my terminal. I could not find it: after rebooting, I had never opened it because I had not needed it.

A readable work summary
DIAPOSITIVE 1 / 1A readable work summaryThe video shows an example of a structured release summary while Theo discusses readable interfaces.

That was when it hit me. Having an interface with more pleasant text, easier navigation, a sensible category system and projects based on where things live on my computer made me code much more.

Sur la même chaîne

5 diapositives38:47EN
Theo - t3․gg· 28 oct. 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.Agents de codeIngénierie d’agentsAI cost & performance+2
5 diapositives36:07EN
Theo - t3․gg· 27 oct. 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 & performanceAgents de codeInference+1
5 diapositives30:37EN
Theo - t3․gg· 26 oct. 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 skillsAgents de codeCode review & verification+2
2 diapositives0:43EN
Theo - t3․gg· 23 oct. 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 diapositives29:22EN
Theo - t3․gg· 22 oct. 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 diapositives31:13EN
Theo - t3․gg· 20 oct. 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.Agents de codeDeveloper productivityHuman-AI Collaboration+1