We share what we learn while building scalable platforms, solving institutional problems, and designing systems that last.
Long-form pieces on engineering practice, AI strategy, and the institutions we build for.
The hidden cost of legacy automation — and how LLM-mediated agents change the economics of back-office work.
Read more
What we learned delivering a national-scale electronic medical record system across 40+ facilities.
Read more
Sometimes the legacy system is fine. Three diagnostics we run before recommending a rebuild.
Read moreEngineering snapshots, code experiments, deployment moments and architecture sketches. The unfiltered feed.
Engineering tip After a 3-month audit-trail rebuild, we moved every table to event-sourced state. Hard problem, but reconciliation got 4x faster.
Code · TypeScript// idempotent retry with backoff export async function retry<T>(fn: () => Promise<T>) { let attempt = 0; while (attempt < 5) { try { return await fn(); } catch (e) { await sleep(2 ** attempt * 100); attempt++; } } }
Architecture We designed the consumer-rights platform as a modular monolith with hard internal boundaries. Same shipping cadence, half the ops cost.
Decision log The relationships are deep but the query shapes are stable. Postgres + recursive CTEs has carried us through 4 platforms now.
Field note Removed every transient notification on the CCMS dashboard. Replaced with persistent status rows. Support tickets dropped 38%.
Quick bit Before we write a proposal, we answer four questions out loud. If we cannot, we politely decline. Saved us 60% of unscoped work.
Templates, frameworks, and reference documents pulled from real engagements, adapted for public release.
A structured framework used across institutional modernization projects: phasing, governance, KPIs, and rollback gates.
Battle-tested ADR templates we use on every engagement: context, options, consequences, and review cadence.
Anonymized workflow diagrams from public-sector engagements: complaint triage, license issuance, citizen onboarding.
The 47 questions we answer before writing a single line of code on a national-scale platform.
Whitepaper on UX patterns that move citizen trust metrics, based on production data from three ministry platforms.
Compliance, security, and SLA reference document we provide to government and enterprise procurement teams.
Patterns for safely connecting to mainframes, SOAP services, and ministry-grade legacy systems without a rewrite.
Reference API docs from CCMS and selected platforms: schemas, auth flows, idempotency, and rate-limit headers.
Whether you're planning a platform, modernizing operations, or validating a product idea, we can help structure the right system.