Escrow is a state machine with money in it
Escrow fails when money can sit in two states at once. Model every state, transition, retry and ledger entry clearly.
ReadInsights
Category: Engineering
How we actually build things: architecture decisions, the trade-offs behind them, and what we would do differently the second time around.
Choosing technology you can still hire for in 2046
Utilities need software choices that can be maintained, audited, rebuilt and handed over across twenty year horizons.
ReadRights expire, and your CMS should know before your lawyer does
The real asset is permission to show content. Your CMS needs rights, expiry, takedown and reporting built into its model.
ReadTwo guests, one seat, and the race condition that costs you both
Accidental overbooking comes from race conditions, stale channels and weak cancellation paths. The target is zero double bookings nobody chose.
ReadBuild for the exceptions, because the plan is already fine
Logistics software earns its keep in the exceptions, where senior people resolve delays, constraints and bad data the plan never shows.
ReadThe evaluation harness is the product spec
If a probabilistic system cannot be scored, it has not been specified. The evaluation harness becomes the product definition.
ReadWhat correctness means at a billion events a day
At a billion events a day, correctness means choosing, bounding, measuring and reviewing the errors each data class can tolerate.
ReadAgents do not need more intelligence, they need narrower mandates
Agents stall when their authority is undefined. Narrow mandates make scope, ownership, audit and reversal clear.
ReadBuilding for a site with no signal
Construction software fails when it assumes a signal. On site, the device must record work locally, sync later and keep evidence intact.
ReadSchool bandwidth is a design constraint, not an excuse
Education software fails when it is designed on fast office fibre but used by whole classes on shared school connections and older devices.
Read
