Youness Aamiri
RSS FeedI build systems where being wrong is expensive — reconciliation engines, IFRS9 pipelines, insurance rating logic. Five years in fintech and insurance taught me the same lesson twice: correctness and performance aren't separate concerns you trade off against each other, they're the same discipline applied at different scales.
That's the thread running through the CedarRecon / CedarRisk engines and BenchmarkGate — a reconciliation engine, an insurance rating engine, and the tool I built to stop performance regressions from shipping silently. I write about what actually happens when you take a domain model seriously and then find out it doesn't scale.
Featured
BenchmarkGate, Part 4: benchmark-gate compare, and Why Order Matters
Splitting 'what changed' from 'is that acceptable' into two commands — and why compare has to run first.
Recent Posts
BenchmarkGate, Part 3: benchmark-gate validate
Six validators, three file types, one command — catching a broken policy file before it breaks check.
BenchmarkGate, Part 2: Why a Baseline Isn't Enough
A policy file, a stability gate, and 21 benchmarks that correctly refused to give an answer.
BenchmarkDotNet Measures Performance—But Who Enforces the Budget?
BenchmarkDotNet gives you excellent performance measurements — but no opinion on whether a number is acceptable, no memory of yesterday's baseline, and no way to fail a build. Here's the gap, and what I'm building to close it.
From dictionary to columnar: how we made a .NET financial reconciliation engine 2x faster
How CedarRecon's exception classifier went from 1,368ms to 646ms per million transactions, and the four optimizations that made things worse before it got better.