Why Non-Developers Are Building Better Software Than You Think
featuring Jose Duarte
I talked with Jose Duarte about building real software with AI without a traditional CS background, and why clearer planning now beats raw coding speed.
Most people still think software requires a traditional developer path. That assumption is getting outdated fast.
In this episode, I sat down with Jose Duarte. He leads growth at Pangea Money Transfer, and he is building real products with AI workflows even without a computer science background. Not toy prompts. Actual iOS apps, API integrations, and multi-agent flows that mirror how serious teams ship software.
What I like about Jose's approach is that he does not treat AI like a slot machine. He treats it like a team that needs structure. Requirements first. Planning first. Then implementation with constraints. That single shift is the difference between random output and useful output.
One of the biggest points we covered is that AI systems move fast, but they can still go in the wrong direction quickly. If you do not define scope, guardrails, and success criteria, you can burn hours rebuilding things that should have been clear from the start.
We also talked about using AI to simulate a pre-build meeting. I use this pattern too. Let the model interview you before writing code. Ask what the edge cases are, what the data model should look like, and how failures should be handled. That up-front friction saves a lot of back-end pain.
Another important takeaway is cost dynamics. The cost of starting over is now much lower than it used to be, which changes strategy. You can prototype faster, test faster, and kill weak ideas earlier without carrying months of sunk effort.
At the end of the day, this is not about replacing developers. It is about raising the number of people who can turn ideas into working software. The winners are going to be the people who combine domain knowledge with good workflow discipline.
If you are building with AI right now, focus less on vibe and more on process. That is how you get repeatable outcomes.