Over the last three months, I’ve built three working products. A WhatsApp outreach tool with CRM and a mobile version. CallCoach — an iOS app in Swift that recognizes speech in real time and suggests replies. And one more service that’s currently in development.
I’m not a developer. I don’t have a formal education in programming. I’m a product designer — I understand systems, I know how to think in scenarios, I know how a product should work. But until recently, between “I know what’s needed” and “it works” stood a developer.
Now between us are Claude Code and ChatGPT Codex.
What’s changed
Before, I had an idea and a brief. I described the task to a developer, they built it, I tweaked it, and we iterated. It worked — but slowly, expensively, and with losses in translation.
Now I have an idea and a conversation with a tool. I describe the task — in detail, with logic, with edge cases. The tool writes the code. I run it, see what’s off, explain, and iterate. No losses in translation — because I’m in the conversation myself.
That doesn’t mean I’ve become a developer. I still don’t know the syntax by heart, and I don’t read someone else’s code like a book. But I do know what I want to get — and I can explain it precisely enough to get a working result.
So who is the creator now?
That’s the question I’ve been thinking about over the past few months.
When the machine writes code — and the person defines the task, checks the logic, makes decisions about what matters, and is responsible for the product doing the right thing rather than just working — which one of them is the creator?
I think the boundary is shifting. Before, the creator was the one who could make things with their hands. Now the creator is the one who can think — ask the right questions, hold the context, understand why it’s needed.
Technical skill is no longer the entry ticket. Something else is. Let’s call it product thinking — the ability to see the system as a whole, understand the user, and make decisions under uncertainty.
What this means for designers
Design has always been about understanding human experience. About how people think, what they need, where friction appears, and how to remove it.
Now a designer with that understanding can build not only interfaces — but entire products. Fast, affordably, solo.
That changes the profession. Not destroys it — changes it. A designer who knows how to work with machine intelligence tools becomes something bigger than a designer. And something different from a developer.
There isn’t a new word for it yet. But the people are already here.
I’m one of them. Figuring out what it means right now — in practice, with real products and real users.