Studies and case studies
Research & Engineering
Two kinds of long-form work. Studies are controlled experiments on how AI systems fail, each with a preregistered plan, a benchmark built for the question, and results reported whether or not they support the original idea. Case studies are engineering retrospectives on systems I’ve worked on, with every figure defined and every simplification labelled.
- Independent research202611 min read
RAG Autopsy
When the Knowledge Base Disagrees With Itself
Most RAG evaluation asks whether a system can find the right evidence. This study starts one step later: every condition gets the same documents, and those documents disagree. 155 held-out cases, six conditions, 1,061 generations.
LLM EvaluationRAG ReliabilityRead the study → - Engineering case study202610 min read
Ticket by Ticket
State, Recovery and Throughput in a Zendesk-to-Jira Migration
A retrospective on the Python tooling behind a Zendesk-to-Jira migration of 10,000+ support tickets: per-ticket state and recovery, and rolling concurrency of up to six tickets. ~99.8% migration success, and about 5.4× the throughput of the first, sequential version.
PythonSystems IntegrationState & RecoveryConcurrencyRead the case study → - Personal project202616 min read
PulseWatch
Teaching a Wearable to Notice It Isn't Being Worn
I kept taking my Fitbit off and forgetting to put it back on. PulseWatch is one Cloudflare Worker that reads the Google Health API every minute, decides whether missing data really means the tracker is off, and sends a Telegram reminder: an explicit state machine, 30-day personal baselines, a transactional outbox, and what production changed in its first two days.
Cloudflare WorkersTypeScriptState MachinesWearablesRead the case study → - Workplace tool202615 min read
OneSpot
Giving the Office Parking Chat a Referee
The office parking group chat, rebuilt as a Microsoft Teams app: release your paid space on days you're out, and a colleague claims it in one tap. One invariant enforced three times, from domain rules to PostgreSQL triggers, so that when ten people press Claim at once, exactly one gets the space.
Microsoft TeamsPostgreSQLConcurrencyTypeScriptRead the case study →