I’m a fractional CTO, software architect, and AI and LLM engineer. I help startups and scale-ups build engineering cultures that hold up, architectures that survive contact with growth, and teams that actually ship.
Most of my work sits where those three meet. A team that ships badly usually doesn’t have a people problem or a code problem on its own. It has a problem in the seam between them: an architecture nobody can reason about, or a process that quietly punishes the safe move.
Day to day that means Go, PHP and React, cloud infrastructure, and increasingly the messy business of putting language models into production paths where correctness matters and the bill is real.
What this blog is for
The longer arguments. Architecture decisions and the tradeoffs behind them, not just the conclusion. What AI features actually cost to run once they leave the demo. The parts of engineering leadership that don’t compress into a short post.
I’d rather publish one thing worth disagreeing with than a steady stream of things nobody could object to.
First posts are coming soon.
Elsewhere
Until then, find me on LinkedIn, on GitHub, at robinverlangen.nl, or by email at [email protected].