I'm not a developer. I can read code roughly, the way you might read a menu in a language you studied in college. I get the gist. I can't write it. But I'm shipping things I never could have built two years ago, and the gap between "person with ideas" and "person who builds things" is closing fast.
I've been deep in Cursor for months now. When I checked my usage dashboard, I thought I was a power user. Then I saw the global rankings and realized I was barely in the top 100 at my company. That was a reality check. So I reached out to the person at the top of the list and asked how he worked. His advice was simple. Use it for everything. Not just code. Research, writing, learning, data analysis. Don't assume you know what it can't do, because that boundary moves every week.
That changed how I think about these tools. I stopped treating AI as a code generator and started treating it as a thinking partner. As a generator, it handles the mundane. I'm the judgment. I'm the arbiter of taste. I know what good looks like for users because I've spent twenty years learning that. The tool doesn't replace that knowledge. It removes the bottleneck between having the idea and seeing it exist in the world.
Here's what I've learned through months of experimenting with vibe coding tools. The ones that win aren't the ones with the flashiest AI. They're the ones that understand what a non-engineer actually needs. Designers don't think in functions and classes. We think in flows, states, and interactions. The tools that translate intent into working software without requiring me to think like an engineer are the ones I keep coming back to.
But I want to be clear about something. These tools don't make you a developer. They make you dangerous in a good way. You still need taste. You still need to understand the problem deeply. You still need to know when the output is wrong, even if you can't articulate why in technical terms. AI handles execution. You handle the "should we."
I'm not waiting for the tools to get better before I start building. I'm building now, learning as I go, and sharing what works. That cycle of learning, building, and teaching is how I've always operated. AI just made the loop faster.