Loading article
Schemas, validation and the layers in between — the work that decides whether a number on a screen can be trusted, and where a rule has to live so it cannot be bypassed.
Splits, bonuses, reinvestments and side-pockets each break a naive holdings model in a different way. What a corporate action actually is, and why it has to be a ledger entry.
NAV files arrive late, arrive twice, and get revised. Notes on building import and valuation pipelines for a wealth platform, where being roughly right is the same as being wrong.
Choosing Postgres took ten minutes. Choosing a code-first ORM took longer, and the bill arrives as the five kinds of database object it cannot generate.
The multi-tenancy decision you make in week one and pay for in year two, and why we moved isolation out of our code and into Postgres.
Integrating with registrars, KRAs and custodians, where the documentation is a PDF from 2016, the webhook may not arrive, and two authoritative systems disagree about the same holding.
At 3,500 schools a loose rule is not a theoretical problem. A duplicate admission and a payroll calculation that existed in three places, and what they taught me about layering.
All articles in chronological order, or get in touch if this is the kind of problem you’re working on.