The Region Beta Paradox of Modern Coding

Feb 26, 2026

You would have experienced this paradox in scenarios other than coding.

You would walk half a mile to reach somewhere in 10 minutes, whereas you would drive to reach your workplace 2 miles away and get there faster. A minor back pain is ignored for years, while an acute fracture is immediately taken care of.

The mild inconvenience never triggers a response. The intense one forces you to act, and acting makes things better.

Something similar is happening in the coding agents space.

The comfortable middle

Earlier, users started using tab complete models extensively. They provided the right amount of control and productivity boost. The feedback loop was tight: you typed, the model predicted, you accepted or rejected. It felt like a natural extension of how developers already worked.

Now with better long-horizon models, users have increasingly adopted agentic workflows. Michael Truell’s recent thread about Cursor’s evolution captures this shift clearly: in March 2025, Cursor had roughly 2.5x as many Tab users as agent users. That ratio has now flipped — they have 2x as many agent users as Tab users, with agent usage growing over 15x in a single year.

The paradox

When you use tab completion, you write code 20–30% faster. That feels good. You’re still walking in the rain, just slightly faster.

But when you hand off 35% of your PRs to autonomous cloud agents — as Cursor’s own team now does — everything has to change. Your tests can’t be flaky. Your environments can’t be brittle. Your task descriptions need to be precise enough for a non-human teammate to act on independently.

The pain of that reorganisation is sharp enough to actually trigger a deeper structural response — and that’s exactly what makes it productive.

This is the paradox. The mild productivity boost of tab completion was comfortable enough to never demand change. Autonomous agents are disruptive enough that they force it.

The agent-first developer

The amount of code generated by agents is increasing rapidly, making agents the default option for coding.

Truell describes developers who have fully embraced this shift as having three traits:

• Agents write almost 100% of their code
• They spend their time breaking down problems and reviewing artifacts
• They spin up multiple agents simultaneously instead of handholding one to completion

The adoption curve is probably skewed toward power users. Lots of programmers have not yet experienced the capabilities of the latest coding agents. Many are still in the tab completion zone — productive enough to feel modern, not disrupted enough to transform.

What comes next

Agentic coding patterns require a lot of structural changes in organisations that have traditionally been slow to move.

I predict new companies will skip tab-completion-based coding entirely and directly start with an agent-first approach for building software. They won’t carry the baggage of workflows designed around human keystroke productivity. They’ll structure their codebases, their specs, and their review processes for agents from day one — and that head start will compound fast.

The region beta paradox tells us that the comfortable middle is often the trap. In coding, that trap is tab completion.

The teams and companies that push through to the acute discomfort of agent-first development will be the ones that come out faster on the other side.