Engineering notes: what we built, what we broke, what we took away.
-
Our domain layer contains nothing but exceptions. On purpose.
Nine contexts, twenty-nine commands, a single query handler, zero ports. What we kept of DDD and hexagonal architecture, what we turned down, and the five places infrastructure crosses the boundary anyway. This is not purist DDD, it is time to market.
-
We were our own best customer. That was a bug.
Our company publishes on our platform — and was counting itself in our revenue, our funnel and our follow-up lists. How we took it out of the statistics without taking it off the site.
-
The cheapest feature is the one you don't build
Three signals that say 'do not write this code' — and what they saved us in a single day.
-
Upgrading the OS under Docker: what is still coupled, and what nothing validates
The application lives in an image, so the distribution cannot touch it. Four coupling points remain — and one of them sits in a blind spot no pipeline covers.
-
Building a complete, production-ready SaaS with a coding agent
Zero-downtime deploys, real payments, passwordless sign-in — paired with an AI.
-
Guaranteeing legitimate case studies without a moderation team
Betting on verified identity rather than censorship — and the two bugs that made us doubt it.