Über mich.
Architekt, Autor, Gründer — an den meisten Tagen in dieser Reihenfolge.
I design the systems other systems rely on. In practice that means event-driven architecture in PHP/Symfony and Go: append-only ledgers, saga orchestration, anti-corruption layers over legacy cores that let new work ship without asking permission from the old.
I came to this the long way — through years of CRUD monoliths that were fine until they weren't. Domain-driven design gave me the vocabulary for what was going wrong, and event sourcing gave me somewhere to put the truth. Most of what I write is an attempt to pass on the judgment those tools demand, because the patterns are easy and the judgment isn't.
What I do now
I run AnvilaTech, a small engineering firm delivering these systems for logistics and fintech clients. I take a limited number of architecture engagements a year — usually scoping, an audit, or leading a migration that someone has been putting off.
If you're here to hire me for commercial work, AnvilaTech is the right door. Everything else — questions, corrections, arguments about aggregates — reaches me directly.
Beyond the terminal
TODO — owner to supply. This is where the hobbies, workshop, and off-hours photos go; the gallery below is ready for them.
Talks and conversations
TODO — owner to supply the recording and podcast files. Both players below are wired and will render real media as soon as it exists in the CMS.
How I work
- Model the domain before the database. The schema is an outcome, not a plan.
- Make the expensive decisions reversible; make the cheap ones fast.
- Write it down. An architecture nobody can explain is an architecture nobody can maintain.
- Leave the system legible enough to hand off. That's the actual deliverable.