I am the one who builds it — and the one you reach when it breaks.

Three things that make the difference

1. Design and engineering in one person

   I studied media informatics. The subject is half computer science and half the question of how people use software. So I can explain why an interface looks the way it does, and I also build it myself. You do not have to carry anything back and forth between a designer and a programmer. That handover is often the most expensive part of a project.

2. I run what I build

   I currently keep looking after seven projects myself: four on the web and three apps. I roll out new versions, back up the data and notice when something goes down. That changes how you build. Someone who gets the call when it breaks at night decides differently from someone who closes the project at launch.

   See the projects

3. I say so when I got it wrong

   On one client project I found a mistake of my own in my own final review and wrote it down. On one of my own products I threw away four months of work because the review pointed elsewhere. It is written here so you know what you get when something does go wrong.

   How a project runs