How Does Thariq Shihipar Treat the Bitter Lesson?

Thariq Shihipar treats the bitter lesson as a rough stand-in, and he flags the label as a misuse. Harnesses go out of date very quickly, and how they change is unintuitive. The bitter lesson itself is about scaling and compute.

The obvious break was the jump from chat to agents, which required entirely new tools. A newer break is a model that can modify its own harness. An own-harness loop, or building an artifact, uses capabilities the model already has. Models now hold more intelligence than the average software engineering task. He reaches for the Jacobian contract as a Terminal Bench example and then withdraws it ("Not really"), while keeping the claim that the tasks are quite complex and that he would not have been able to do the work as a software engineer. The version in view was TB3.

The goal is still user value. An infinite space of work leaves two routes: spend compute, or keep the user in the loop so the day ends with the right decision, the right output, and the right artifacts. Mods are one way of spending that intelligence. Claude Code still has the core of an agent loop, and the loop has gotten more complicated.