How I work
AI-assisted software development, with human judgment at every stage.
From ideas and concepts to applications and platforms in production. I work in short cycles, delivering value from the very first one.
How I do it
My method behind every project
I oversee, test, and approve every deliverable. Nothing reaches production without passing through my judgment.
Understand what actually needs solving
Before designing anything, I invest time in understanding the real problem, not the symptom. This shapes everything that follows.
Define architecture and roadmap
With the problem clear, I design the system architecture and we build the project roadmap together, the foundation everything else is built on.
Short cycles
No months-long projects locked in from the start. Cycles of weeks, each one delivering real value.
Evolution and monitoring
Once in production, I review how it's performing, apply updates, and add improvements as the business needs them.
Understand what actually needs solving
Before designing anything, I invest time in understanding the real problem, not the symptom. This shapes everything that follows.
Define architecture and roadmap
With the problem clear, I design the system architecture and we build the project roadmap together, the foundation everything else is built on.
Short cycles
No months-long projects locked in from the start. Cycles of weeks, each one delivering real value.
Evolution and monitoring
Once in production, I review how it's performing, apply updates, and add improvements as the business needs them.
It's not "vibe coding"
It's judgment, with AI as a tool.
I use AI to write code faster. It's a real advantage, for you in final cost and for me in speed. But that's where the resemblance to letting AI decide on its own ends.
I define the experience, the architecture, and the technical spec. With those definitions in place, I have AI build while I move forward in parallel on other fronts of the project. When it's done, I review every deliverable: I read the code, run the tests, and assess how solid, secure, and scalable the solution is. If something doesn't hold up, I fix it or redo it. AI speeds up execution, but the decisions (what gets built, how, and whether it's ready) are mine to make.
This process lets me deliver more robust, secure, and scalable solutions, and do it faster than with traditional development.
My stack
Why Laravel
I choose Laravel, PHP's most established framework, because its ecosystem serves everything from small applications to large enterprise systems, without sacrificing solidity.
Proven robustness and security
A mature ecosystem, built on years of work in systems where a failure has real consequences.
Speed, even in large systems
The way it's built lets you move fast without losing order, even in complex projects that grow over time.
AI built in natively
Thanks to the AI SDK, you can build applications with AI as a real part of the system, not bolted on from the outside.
NativePHP for native mobile
Real mobile apps, without leaving the same ecosystem or duplicating logic in a separate stack.
Companies and organizations that trusted my work
