Theo on the Three Virtues of Great Programmers

Laziness, impatience and hubris sound like flaws, but Theo explains how they can motivate useful automation.

ThTheoSpeaker
Channel
Theo - t3․gg
Published
Jun 11, 2026
Video
0:27
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 revisits the three programmer virtues—laziness, impatience and hubris—and describes how each can motivate someone to improve and automate a repetitive task.

  1. 1Three surprising virtuesTheo names laziness, impatience and hubris as traits that can help programmers automate and improve things.
  2. 2Impatience and confidenceImpatience motivates a fix, while hubris encourages a programmer to believe they can build it.
  3. 3Make the fix lastLaziness encourages a solution that does not demand constant attention afterward.

Takeaways

  1. Impatience can motivate a programmer to fix a frustrating problem.
  2. Hubris can provide the confidence to attempt a solution.
  3. Laziness can motivate a solution that reduces repeated work and maintenance.
FULL TEXT

Read the edited text by chapter

Transcript only
01

Why these traits can help

Theo names three traits that normally sound negative. He relates them to programmers' work of automation and improvement.

I still remember learning about the three virtues of great programmers: laziness, impatience and hubris. Those usually sound like terrible traits, but programmers are supposed to automate things and make them better, so they can be useful here.

02

Fix it and avoid repeating it

Impatience drives the fix and hubris supplies confidence. Laziness motivates a solution that needs less maintenance.

If you're impatient, you want to fix the problem. If you have hubris, you think you can do it. And if you're lazy, you try to solve it in a way that doesn't require you to keep coming back and maintaining it. That's why I think these traits work so well for programmers.

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