There is a feeling I haven’t felt in over a decade.
If you built digital products in the late 2000s or the early 2010s, you probably know the feeling I'm talking about. Back then, the lines between designing and building were thin. You were a full-stack builder. You didn’t need a massive team, millions in funding, or weeks of alignment meetings to bring an ambitious, crazy idea to life. You just sat down, wrote the code, and shipped it.
But after that, the complexity exploded. Suddenly, building required bigger teams, heavier funding, and endless layers of organization. It became almost impossible to create anything transformative on your own. As the industry matured and hyper-specialized, we drifted away from being builders of product. We became managers of alignment, curators of static Figma snapshots, and authors of requirements pages rather than builders of the real thing. It was still possible to build something alone, but the friction was immense.
Lately, though, that old builder feeling is back. It feels like a genuine renaissance.
Thanks to LLMs, we are reclaiming a level of individual agency and impact that seemed lost. But this shift isn't just about speed, or bypassing the engineering queue.
The real shift is that we are no longer looking at the surface of a product. Instead of building pixel copies of a few key moments—which, until now, were the only proxies we had—we can go deeper and think about how the system actually works. We build the system itself, and then overlay the interface on top.
In the hyper-specialized era, having a new idea meant paying an immense tax on curiosity. You had to write pages of product specifications, build slide decks to explain the vision, and spend weeks in meetings trying to align stakeholders. You had to justify the cost of simply trying.
By the time you reached the level of consensus needed to write the first line of code, the original spark was already diluted, or the initiative was dead on arrival.
Today, that barrier has vanished.
When you can build a dynamic, behavior-driven model in a couple of days on your own—something fueled by realistic data rather than static assumptions—you don't need to ask for permission. You don't need to write a PRD or pitch a slide deck. You just hand people a working experience that they can interact with, feel, and learn from.
A working prototype collapses debate. In meetings, instead of debating abstract assumptions about how an interface might behave, you just run the code. The conversation shifts from politics and persuasion to raw substance.
This is a fundamental shift in agency. When the distance between a raw idea and a working reality is virtually zero, the balance of power returns to the builders. We can stop looking at the surface, stop managing the alignment loop, and go back to what we did best: making things real.