About me
I build software that has to work in practice
I am a web developer. I build websites, web shops and web applications for businesses, and I work on my own technical projects. Triomia is the name under which I show that work.
How I work
Four things you can expect from me.
Understand first, then build
I want to know what your business actually needs before I propose anything. Sometimes that is a new site, sometimes a small change to what is already there.
Plain language
You do not need to know the technical terms. I explain what I am doing and why, without jargon.
Honest advice
If something is not needed, or not realistic within your budget or timeline, I say so straight away.
Careful with data
I take security and privacy into account from the start, not as something bolted on afterwards.
What I build
Websites and web shops, online booking and reservation systems, and custom web applications: from the front end visitors see to the back end that calculates prices, handles forms and sends emails.
I also automate repetitive work and connect websites to other systems. With an existing website, I first find out what already works well before replacing anything.
A concrete example is the AquaFun Scheveningen website: three languages, a booking wizard with live price calculation, frequently asked questions and contact over WhatsApp.
AI as a tool
I use AI tools for analysis, building and testing. They make parts of the work faster.
What they produce is still software that I understand, check and test myself before it goes live. The responsibility stays with me, not with the tool.
Client work and my own projects
Alongside client work, I build my own technical projects. The largest is Cipher: an experimental programming language that explores whether a compiler can enforce that sensitive data does not end up in the wrong place.
Cipher is research, not a product. It is where I go deep on hard technical problems, and what I learn there carries over into everyday web work: handling data more carefully, and spotting earlier where something could go wrong.
One point of contact
The same person discusses what you need, builds it, tests it and explains it at handover. You always know who to talk to.
Where to go from here
See the work, or get in touch.