The short version
Founder of Vi3ecoding. Over 11 years in web design. More than 100 client projects shipped for freelancers, local businesses and growing brands. Not a traditional software developer — a builder who learned to translate business problems into working products.
Today I do the same thing, faster, with AI doing the typing.
Where I came from
I didn't start in computer science. I started in client work. Restaurants that needed a website. Studios that needed a redesign. Small brands that needed a digital footprint that actually converted.
Over a decade of that teaches you something most engineering bootcamps don't: businesses don't want code. They want outcomes. They want a working booking page, a clean menu, a checkout that doesn't lose customers.
After more than 100 of those projects, I stopped seeing problems as technical and started seeing them as patterns. That shift turned out to be the most valuable skill I had — long before AI made it obvious.
The turning point
Then a conversation with Andreas Kunz introduced me to Lovable. That single conversation changed how I work.
What started as curiosity quickly became a new workflow: ChatGPT for thinking, ChatGPT for requirements, ChatGPT for project planning, Lovable for implementation, human judgement for every real decision.
I didn't have to give up the craft. I had to redefine my role inside it.
What I actually learned
AI doesn't remove the need for experience. It amplifies it. The better the context, the better the outcome — and good context comes from years of being in the room with real customers, not from prompt templates.
Years of client work suddenly became more valuable, not less. The bottleneck moved from typing to thinking. From shipping to deciding what to ship.
Why Vi3ecoding exists
There's a wave of non-developers, freelancers and small business owners who have ideas but no team. The old answer was: hire someone, spend €20k, wait three months, hope it works.
The new answer is: learn to direct AI tools yourself. Keep the strategy and the editorial control. Let the AI do the keyboard work.
Vi3ecoding exists to make that practical. Not to teach people how to code. To help people build.
How I work now
I take on more projects per quarter than I ever could before. I price by outcomes, not hours. I spend more time writing briefs and reviewing diffs than writing implementation code.
The work feels closer to editing a magazine than writing a novel. That trade has been worth it — for me, and for the clients on the other end of it.