AI-first software development and modernisation
Modernise and Build Software With AI Tools, Steered by a Developer
You need new software, or nobody wants to touch your old software any more. AI tools take over the routine work, and a developer takes responsibility for the result.
AI-first software development means AI tools take part in every step: writing code, testing, documenting and upgrading. The architecture and the technical decisions stay with a developer. That holds for new software just as much as for an old application you want to keep using.
What is AI-first development, and what is vibe coding?
In AI-first development the AI writes much of the code, but a developer steers, checks and decides. In vibe coding someone tells the AI what they want and accepts the result without judging the code themselves.
More detail
For a quick prototype that can be enough. For software that a business runs on, the principles of software development stay important: a clear architecture, version control, tests and review. Without them you can get stuck, because nobody understands what was built.
What does the developer do when the AI writes the code?
The developer’s role is strategic and the AI’s is tactical: the developer sets the direction, and the AI carries out the individual steps. I steer the work and keep the overview.
More detail
Along the way the AI surfaces routes, and I explore them. Some I reject as irrelevant, others I keep in mind for a later phase. I also make sure the code is complete: a coding agent must not stop before the task is done.
Is AI-written code safe enough to run a business on?
Yes, if it passes the same checks as any other code. Nothing goes into your business before automatic tests have passed and I have reviewed what matters.
More detail
Changes go through version control, static analysis and automated tests. The code sits in a repository you can access. AI tools deliver drafts and take over the routine work. The technical decisions are mine.
What changes for me as the client?
A developer with AI tools can now take on work that used to need a small team.
More detail
Tests and review stay, and the responsibility rests with one person who talks to you. I use the tools to hand off routine work, not to skip steps.
Can you take over or modernise software another developer left behind?
Yes, it is a large part of this work. I need code and access, but not a handover from the previous developer.
More detail
I work my way through the code, the repository and the deployment history, so that the next steps can be planned again. If a shop is a long way behind the supported version, that means an upgrade in stages while the shop keeps selling.
For client upgrades I use an AI-assisted workflow with Rector, a tool that rewrites PHP code automatically by defined rules, and Claude Code. How it runs is in the article on AI-assisted Magento upgrades. Whether repairing, extending or replacing is the right way is decided once I have seen the application. The first step for that is the Code Check below.
Is one developer enough?
For a lot of work, yes. I cannot replace a whole team working in parallel, or support that is staffed around the clock.
More detail
If your project needs that, I will tell you so in the first conversation. What happens if I am unavailable is answered on the page about me. I do not build anything that only runs while I am reachable: what I build should be something somebody else can carry on.
Will I own the code?
How the rights to an application are settled is in your contract. You always have access to the repository the code sits in.
More detail
What counts in practice is that the code does not live only with me, and that somebody else can carry it on.
My View of the AI Hype
There is a lot of hype about AI right now, and many businesses are trying to work out how to use it well. I take a pragmatic approach, keep an eye on trends and try them out before I offer them to clients. Often my thinking as a developer matches that of others, who then put it into words.
My conviction is that the principles of software development stay important even in the age of vibe coding. As far as I know, vibe coding is mostly what non-developers do, and it can leave people stuck. My experience helps me judge which technique fits which need, and also when a task needs no AI.
What I Build It With
PHP and Symfony. Two examples from real work.
The first reads product data from a supplier. The endpoint serves XML rather than SOAP, so there is no WSDL and no generated client: fetch the document, parse it, transform it, and import it into Magento, which at the time meant CSV. The unglamorous part is the point. Between two systems there is rarely a beautiful API, and usually a format you have to work with.
The second is middleware between a chatbot and the checkout: thin Symfony services that each do exactly one job and keep that logic out of the shop.
I do not name either client here. That is the normal case for this kind of work, and it means these two paragraphs are description rather than proof.
When AI-First Development Is Not the Right Answer
I will advise against it if one of these is true:
- A standard product can do what you need. Then you should buy it.
- A fixed workflow between your systems is enough and needs no application of its own. More on that on the AI automation page.
- You need a whole development team, or support that is staffed around the clock.
In that case I will say so in the first conversation, and you save yourself the check.
The First Step: the Code Check
The Code Check costs €890 fixed. The written result arrives within 5 working days of receiving code, access and a database copy. It contains:
- the installed packages and framework versions
- the distance to the currently supported version
- the three largest risks
- a cost range for what you want to build or renew
A fixed written quote for your change follows. Book the next step within 30 days and the €890 is credited. I offer a full code review only when the check shows the need.
If you have no software yet, the first step is the free 30-minute conversation, not the Code Check.
And the Work Around the Software?
Sometimes no application is needed. If a fixed workflow is enough, read on at the AI automation page. For tasks where someone has to decide every time there is the AI agents page, and for answering customer questions the AI chatbot.
Frequently Asked Questions
Will you take over somebody else’s code?
Yes, and it is a large part of this work. I work my way through the code, the repository and the deployment history. A rebuild is rarely the first step.
Rebuild or carry on developing?
That is decided after I have looked at the application, not before. Anyone answering that question without reading the code is selling you an opinion.
Do you only work on shops?
No. The focus is e-commerce, but the earliest integration in my records is a sports ranking from 2003 that had nothing to do with retail.
What happens if you are unavailable?
Then somebody else can carry on, because I hand over and document the work. I do not build anything that only runs while I am reachable. That exact problem is why clients call me in.
What do you run that nobody wants to touch any more?
Describe what the application does, who needs it, and what happens if it stops for a day. The first conversation takes 30 minutes and costs nothing, and I will say honestly whether and how I can help.