Architecture that survives contact with a deadline: splitting a monolith, choosing between cross-platform and native, writing code that moves money, and the unglamorous work that decides whether a deploy is something you dread.
An AI-built prototype arrives with one index per table, a secret in the bundle and no schema history. Where the break-even sits, and what to repair.
Five things payment code needs from the first commit: an idempotency key scoped to an intent, integer minor units, an append-only ledger, a replay-safe webhook handler and a nightly reconciliation against the provider.
Idempotency key retention derived from the counterparty’s published replay horizons: 24 hours outbound, 35 days inbound, and the storage arithmetic for both.
Dimensional query containers stopped applying layout containment in 2024: what container-type still does, where the specifications disagree, and when clamp() wins.
What a service split actually fixes, why a shared schema leaves you with a distributed monolith, and which service to extract first.
The parts of a mobile app that still have to be native, what a native module costs across a year, and why hiring only gets a vote once hardware has abstained.
A Postgres helper left at the default VOLATILE costs an index condition and a row estimate: a tenant holding 0.1% of 40,000,000 rows reads all of them.
What a mobile ship estimate leaves out: store accounts, signing identities, a push key, privacy declarations, and the wait your account type buys you.
Plugin maintenance is superlinear in the plugins that own a write path, and the crossover against a half-day-a-month budget lands at 3.45.
Browse by tag
Twenty minutes, no deck. We’ll tell you straight whether this is work we should be doing, and if it isn’t, we usually know who should.
We come back within one business day.
Analytics
We’d like to use Google Analytics to see which pages people find useful. It sets cookies, and only if you say yes. Your choice can be changed at any time under Cookie settings. Privacy