Case studies
How the work actually went
Long-form write-ups of real engagements: what was wrong, how it was measured, what was tried and rejected, and what could not break while it changed. Each one states where its numbers come from and what has been left out.
Biotech · Data platform
The API didn't look slow. It looked broken.
A scientific data API failing as timeouts and 5xx rather than slowness. Five independent problems across schema, query planning, transport and server concurrency, each producing the same symptom.
~70% faster end to end
Figures from measurements committed to the client's repository. Client and partner anonymised.
Integrations · Open source
The contract fit databases. The market wanted SaaS APIs.
An integration contract designed for CRUD-over-a-table, met with accounting and commerce APIs. ~125 vendor actions covered by one reflective dispatcher, and test suites brought to a catalog that shipped without them.
125 vendor actions, one dispatcher
Public MIT-licensed repository. Every figure is a file-level count or a dated commit.
Recognise one of these?
Slow, fragile, and nobody can say why is the situation I work in most often. Thirty minutes is usually enough to tell whether I am the right person for it.
Book a 30-min intro call Free 30 minutes. No proposal on the first call.