Logo
000 / 100
Engineering blog · Field notes

Written by the people doing the work.

No thought leadership, no predictions for next year. Field notes from real projects, written by the engineers who were there: what we built, what broke, and what we'd do differently, including the parts that were embarrassing.

Browse by topic
Architecture diagram of a legacy ledger and a new ledger running in parallel with a balance comparator (illustrative) Architecture Featured
9 min read

We dual-ran two ledgers for eleven weeks. Here's the bill.

Running a new settlement system alongside a twenty-year-old mainframe costs roughly double the infrastructure and two engineers watching a reconciliation dashboard. We were pushed to cut it to four weeks at the halfway point. Three of the nineteen discrepancies we found surfaced after week eight, in month-end processing — which, by definition, only happens monthly.

MDMeera Deshpande Read the note
Evaluation dashboard for a retrieval-augmented system with a golden question set and regression tracking (illustrative) AI
12 min read

Your RAG system is fine. Your evaluation set is the problem.

How we build golden datasets that catch regressions before customers do, why 200 hand-labelled examples beat 20,000 synthetic ones, and the retrieval failure that only appeared when we sorted by document age.

CEClimentos engineering
Structured scorecard and hiring funnel for a work-sample based recruitment process (illustrative) Hiring
7 min read

We stopped asking algorithm puzzles. Retention went up.

Three years of data from replacing whiteboard rounds with paid work samples — acceptance rates, first-year attrition, and the demographic shift we didn't set out to cause but are glad about.

CEClimentos talent team
Ward handover board with bed cards grouped by due time and research notes on the nurse-led sequence change (illustrative) Craft
6 min read

The nurse who reordered our entire roadmap

We had a sensible technical sequence that would have shown clinicians nothing usable for five months. One conversation in week three changed the plan, and the project succeeded because of it.

CEClimentos design team
Cloud cost dashboard showing spend by team, tag coverage and untagged resources without an owner (illustrative) Cloud
10 min read

Half your cloud bill is untagged, and that's the whole problem

A FinOps write-up from three migrations. The savings almost never come from rightsizing instances — they come from finding the four workloads nobody could name an owner for.

CEClimentos cloud team
Route map comparing a model-optimised route with the route drivers actually took, with depot constraints noted (illustrative) AI
8 min read

The optimal route nobody would drive

A model that was 6% better on paper and ignored in practice. What a week of ride-alongs found that two years of telemetry hadn't, and why we now budget for fieldwork.

CEClimentos AI team
Module dependency graph and a rewrite-or-stay decision matrix for a legacy billing system (illustrative) Architecture
11 min read

In defence of not rewriting it

We've talked four clients out of rewrites in the last two years. Three were right to stay put. Here's the framework we use, and the one case where rewriting genuinely was correct.

CEClimentos engineering
Annotated checkout page with numbered accessibility findings mapped to WCAG criteria (illustrative) Craft
7 min read

Our accessibility audit passed. The users still couldn't use it.

Automated checks caught 31 issues. A two-hour session with four screen-reader users caught eleven more, and every one of them was the kind that makes a product unusable rather than merely annoying.

CEClimentos QA team
Runbook coverage and the flow of work from a batch system to an event-sourced ledger, with handover gaps (illustrative) Teams
9 min read

We budgeted two weeks for handover and needed five

An operations team had twenty years of intuition about a batch system that simply didn't transfer to an event-sourced one. What we got wrong, and how we estimate handover now.

CEClimentos delivery team
Monthly letter

One letter a month.

Architecture decisions we got right, and the ones we had to undo. No product announcements, no webinar invitations. Unsubscribe in one click.

  • A decision we got right, and why
  • A decision we had to undo, and what it cost
  • Written by the engineers who did the work
No spam. One email a month, on the first Tuesday.