Clean code, written by AI, directed by me.
Frontend development is AI-driven today. With more than ten years of experience, I direct the AI so the code scales and the things you don't see are right too.
How I can support you
With a prototype as the starting point, from scratch, or as part of your team. Also as the bridge between design and development, with accessibility in the bag if you like.
Grow a prototype
You have a prototype, often built with AI, and it should become a real product. I pick up where you are and bring order to it. No restart.
Build from scratch
A new web app or website, from the design to launch. You get code your team can read and change later on its own.
Work in your team
Your team is short a frontend developer for a while. I work in your code and your routines, agree interfaces with the backend and hand over so it carries on without me.
Why vibe coding alone isn't enough.
With vibe coding, the AI builds exactly what you describe, and it builds it fast. Whatever wasn't in the prompt doesn't exist. That only shows once the app meets everyday use.
The quick prompt
A few sentences to the AI, written from the result. A few minutes later it's there, and you see the path where everything works.
Example prompt:
- Build a page where my team can approve invoices.
Looks good, ship it.
Changes are just as quick. The AI always builds what you give it. Sometimes it suggests something useful on top, mostly it doesn't: there are too many things one could consider. Then the result goes out. With the test data everything runs, and at first glance it does for the first users too.
Example prompts:
- Show the amount and due date too.
- Sort by due date.
The first bug reports
Users are different and rarely stay on the planned path: a long company name runs into the button, an amount shows in the wrong currency, with thousands of entries the list takes forever. Bad connections, other languages, longer texts: none of it was in the prompt.
More prompts for bug fixing
The reported bugs can be fixed, the unreported ones can't. By then, customers may have left. And every fix is a detour: code becomes more code, harder to read, and soon it no longer holds.
Example prompts:
- The long name runs into the button, fix that.
- Show dollar amounts properly.
- The list takes forever to load, make it faster.
Prompted with experience
Someone who has developed for years knows what matters: which foundations hold, where it will get stuck. A hundred percent safe doesn't exist. But the good 80 percent have to be in, and that takes someone who thinks ahead. And this is a very simple example. With security, access rights or payments, a lot more is missing from the prompt.
Example prompts:
- Build a page where my team can approve invoices.
- Added: Load 20 at a time, with search.
- Added: Wrap long names, show every currency properly.
- Added: Show when it's loading and when there's nothing.
- Added: Never send twice if the connection drops.
Why a developer, when AI writes the code?
Because building is no longer the hard part. The hard part is the decisions before it: Does this still scale when your idea grows? What happens on a bad connection or when something fails? Does a user see at once what to do? I ask those questions before the AI builds, and check what it delivers afterwards.
Common questions
Which frameworks do you work with?
With whatever you run. Which framework, which language, which CMS: that's the smallest question today. I read my way in, and you only switch technologies if it really helps you.
Do you write the code yourself, or does the AI?
Both. The AI brings the quantity, I bring the quality: I set the architecture and the rules, direct it and write it myself where it matters. I'm not a vibe coder. Nothing goes out that I haven't understood and checked.
Can you build on our AI prototype, or do you have to start over?
Usually, yes. I look at the code first and tell you honestly what can stay and what should be rebuilt.
Do you do the backend too?
The fundamentals, yes. With AI you can write anything today, but that doesn't mean you should: a backend belongs in experienced hands, just like a frontend. I coordinate the interfaces closely with your backend team and, if you like, set the endpoints the frontend needs, down to the shape of request and response.
What is your hourly rate?
It depends on how many hours you book. On a first call, free and with no strings attached, I'll give you a concrete rate.
Let's talk.
Whether the project is already running or still just an idea. A short call is enough, free, with no strings attached.