Architecture that earns its keep
I'm a freelance software architect who designs systems simple enough to trust, then helps build them. After twelve-plus years and several systems taken from prototype to production scale, I've learned that the best architecture is the one a team can keep changing without fear: clear seams, honest boundaries, and as few load-bearing assumptions as possible.
I've set the architecture for a real-time platform that grew to a fifty-person engineering organisation, rebuilt the conversion core of a document-automation product, and designed browser-side systems doing real computational work. I bring that range to your problem.
What I help with
- Greenfield design — choosing the shape of a new system, its boundaries, and a technology set that fits the problem rather than the hype.
- Architecture review — an honest read of where an existing system will break, what to simplify, and what's worth keeping.
- Scaling structure — turning a codebase a few people share into one a larger team can work in at once: monorepo boundaries, typed contracts, testing, and CI/CD.
How I think about it
I optimise for reversibility. Every abstraction is a bet on the future; the cheaper it is to pull back out when the bet is wrong, the healthier the system stays. I design accordingly, and because I build as well as design, the architecture never drifts away from reality.
Let's talk
I take freelance architecture work remotely, in Dutch or English, on Taipei time, with my availability kept open during European hours. Tell me about the system you're designing or trying to tame.