DEV Community

Amit
Amit

Posted on • Originally published at artificialcuriositylabs.ai

We're All Builders Now

TL;DR

  • AI didn't make building easier — a 2025 METR study found experienced developers using AI tools took 19% longer on complex tasks. The tool is an access enabler, not a simplifier.
  • The gate that moved was technical credential, not judgment. Domain experts who always had the clearest view of the problem now have direct access to execution primitives.
  • The internet democratized information access; AI democratizes creation access. Both left the hard part hard.
  • What didn't move: knowing what to build, conviction, distribution, customer obsession, and the stubbornness to finish well.
  • If you can see the problem clearly and you're waiting for someone with an engineering credential to build it — that argument is gone.

Building was never easy.

Writing software took years to learn. Most people spent careers getting good at it — understanding systems, debugging at 2am, learning the hard way why certain architectural decisions rot over time. That's real craft. Nobody is taking that away.

But access to creation? That was always a different problem. And that's what changed.


The Internet Did This First

When the internet arrived, it didn't make information easier to create or understand. Journalism still required skill. Research still required rigor. Writing a good book was still hard.

What it did was remove the gatekeeping between knowledge and the people who needed it. You no longer had to live near a great library, or know someone who subscribed to the right journals, or have an institution behind you to access what had been written. Geography, wealth, and institutional access stopped being filters. The knowledge was always there. The internet removed the walls around it.

AI is doing the same thing — one layer up. Not to information. To creation.


What Actually Changed

For most of computing history, building digital things required a specific kind of access: the ability to write code. Or know someone who could. Or wait for a roadmap item to survive a planning cycle and land in an engineer's queue.

That wasn't a commentary on who had the best ideas. Domain experts — the consultant who had seen the same broken workflow at forty companies, the operator who knew exactly where the process fell apart every quarter, the analyst who could have told you what the dashboard should show three years ago if anyone had asked — often had the clearest view of the problem. They couldn't build the solution themselves. The execution layer required a credential they didn't have.

AI removed that specific gate. Not by making building easy. By making access to building primitives broadly available — to anyone with a clear enough problem and genuine enough curiosity to try.

Gartner projects the low-code market will hit $44.5 billion by 2026, with 75% of new applications incorporating no-code or low-code solutions. Operations managers are shipping dashboards. Product leads are building internal tools. Finance analysts are deploying apps. The through-line in every case: the tool caught up with the intent. The thing that used to require engineering cycles now requires an afternoon and a clear enough problem statement.

That's democratization. Not simplification.


The Hard Part Is Still Hard

Here's what AI didn't touch: the judgment gap.

Knowing what to build — that's still human. Most people solve the wrong problem. They build clever solutions to the problem they wished existed, not the one that's actually costing someone time and money every week. Domain knowledge plus genuine customer obsession is still how you find the right problem. No model gives you that.

Conviction — the willingness to commit to a specific bet when everything is uncertain — is still human. AI can generate options indefinitely. It cannot choose. The person who can look at an ambiguous situation and say "this specific thing, now, for these people" — that's still the rare thing.

Distribution. Drive. Scaling judgment. The ability to know which customers to listen to and which to ignore. The stubbornness to keep going when it's not working. The clarity to kill something that's not working fast enough. None of that moved.

The METR study (2025) makes this concrete: in a randomized controlled trial of experienced open-source developers working on complex, real-world tasks from their own repositories, those using AI tools took 19% longer than those without. The tool is not a simplifier. It is an access enabler. What you do with that access still depends entirely on what you bring to it.


The Gate Moved, Not the Climb

The analogy that keeps coming up: "The Internet Democratized Information, AI Democratizes Intelligence." That's close. But for builders specifically, the sharper version is: the internet democratized access to information, AI democratizes access to creation.

Both leave the hard part hard. Reading everything ever written about surgery doesn't make you a surgeon. Having access to every building primitive in existence doesn't make you a good builder. What it does is remove the argument that someone else has to build the thing you can see clearly and they can't.

The gate was always at the wrong place. It filtered by technical credential when it should have filtered by judgment, curiosity, and understanding of the problem. That filter is now gone.

Which means the people who always had the deepest understanding of the problem — the domain experts, the operators, the people closest to real pain — now have the tools to do something about it.

That's the shift. Not that building got easier. That access to the act of building got broader.


So What

Builder mode isn't a job title. It isn't a technical credential. It isn't something you earn after enough years in an IDE.

It's an orientation — the decision to see a problem clearly, take it seriously, and do something about it rather than wait for someone else to. That operating mode is available to anyone with the curiosity to look hard at a problem and the drive to show up with something real.

The access barrier is gone. The hard part — conviction, judgment, customer obsession, drive — was always human. Still is.

What I haven't worked out: whether broader access actually produces better outcomes, or whether the judgment gap is wide enough that it just produces more noise. The METR data suggests experienced builders get slower when AI is in the loop on complex work — which implies the thing that separates good builders from the rest isn't access to tools. If that's true, opening the gate changes who can start. It doesn't change who finishes well.


Part 2 of the Builders series. ← Part 1: Builder Is an Operating Mode, Not a Job Title

Top comments (0)