Writing
Notes on decisions we keep having to explain.
Not thought leadership. These are the arguments we end up making in real projects — when to split a service, what a migration actually costs, why an audit log usually is not one.
4 posts
- EngineeringThe real cost of technical debtTechnical debt is not messy code. It is the gap between what your system assumes and what your business now needs — and it is priced in decision latency.3 min read
- HealthcareAudit trails that hold upIf your application can edit its own audit log, you do not have an audit trail. What actually makes access records defensible.3 min read
- CloudWhat a cloud migration actually costsThe infrastructure bill is the part everyone estimates and the part that matters least. Here is where migration budgets actually go.3 min read
- ArchitectureWhen microservices are the wrong answerMicroservices solve an organisational problem, not a technical one. If you have fewer than about twenty engineers, they usually cost more than they return.3 min read
Start here
Tell us the problem.
We'll be honest about the fit.
A first conversation costs nothing and is useful even if you go elsewhere — you'll leave with an architecture opinion and a realistic sense of scope.
- Reply within 24 hours
- No sales sequence