The bitter lesson

The bitter lesson
The next leap in software quality won't come from a better framework or a cleaner architecture. It'll come from a machine that just tries everything and picks what works.

Last week I read "The Bitter Lesson" an essay that AI researcher Rich Sutton wrote in 2019.

http://www.incompleteideas.net/IncIdeas/BitterLesson.html

His argument is simple and uncomfortable: across 70 years of AI research, the approaches that won were never the clever, hand-crafted ones built on human expertise. They were the brute-force methods that just threw more computation at the problem. Chess, Go, speech recognition, computer vision — every time, the "elegant" human-knowledge approach lost to the one that simply searched and learned at scale.

I think web development is next.

We've spent decades refining our craft. Design patterns, architectural principles, clean code philosophies, framework wars. We take pride in writing elegant solutions. And we should — it's been the right approach when humans are the ones writing and maintaining every line.

But an AI writing code doesn't need to be a craftsman. It doesn't need to intuit the "right" pattern on the first try. It can generate dozens of possible implementations, test them, evaluate trade-offs, and pick the most adequate one. Not because it understood the problem deeply, but because computation is cheap and getting cheaper.

It's brute force. And if Sutton's lesson holds, brute force wins.

This doesn't mean developer expertise becomes worthless overnight. But it does mean the value shifts — from writing the code to defining what "adequate" means. From craftsmanship to judgment.

The bitter lesson for us might be accepting that the next leap in software quality won't come from a better framework or a cleaner architecture. It'll come from a machine that just tries everything and picks what works.