How it is built
Architectural choices explained with the code in front of us: what worked, what we rebuilt and why.
Newsletter
What we learn while building software
A few emails a year: multi-tenant architectures, MCP servers, automated testing. Real cases taken from the projects we run in production, not press releases.
What you get
Three things, none of which is advertising
What went wrong
Mistakes are expensive; telling them makes them useful. Real diagnoses, with how we found them.
Only when it matters
No editorial calendar: we write when there is something to say. One click to unsubscribe.
Subscribe
Leave us an address. Name and company are optional: they only help us write less impersonally.