Writing · 15 pieces
Each of these is a thing that broke, and what it taught
No tutorials and no takes. Every piece is a decision from a system I shipped, written while the reasoning was still fresh: what the obvious answer was, why it was wrong, and what it cost to do it properly.
01
A delivery made offline at 14:02 arrives at 17:00, against a job the office reassigned at 14:30. Every obvious answer to who wins is wrong, and the right answer is not a technical one.
2 min read
Read →02
I wrote the conflict resolver wrong the first time. Four tests went red in under a second and told me exactly what I had misunderstood.
2 min read
Read →03
A driver phone must hold a working credential for nine hours with no way to check in. The standard playbook does not work here, and pretending it does would be the first vulnerability.
2 min read
Read →04
The same allowlist, the same resolver, the same logic. Move one check after the other and an attacker can smuggle a price change through a genuine delivery.
1 min read
Read →05
Seven real defects found by running the system end to end rather than trusting six green test suites. The worst one reported success while writing nothing.
2 min read
Read →06
A pharmacy till has to keep selling when the internet drops, then reconcile without recording a sale twice. That constraint decides the whole architecture.
1 min read
Read →07
IoT vehicle locks speak a proprietary binary protocol over raw TCP. Riders speak HTTP. The operator dashboard speaks WebSocket. All three have to agree on the state of one physical scooter.
1 min read
Read →08
Tens of thousands of products from a third-party supplier, continuously synchronised. The bugs here are not in the fetch, they are in the clock.
1 min read
Read →09
A production marketplace responding in six seconds. The instinct is to suspect the sockets or add a server. Profiling said the database, and the fix cost nothing to run.
1 min read
Read →10
A retailer already ran their business on an external ERP. Building a customer platform in front of it means deciding, per entity, which system is allowed to be right.
1 min read
Read →11
A retail client wanted to rearrange their storefront without filing a ticket. That single requirement is what made GraphQL correct and REST wrong.
1 min read
Read →12
Holding money between two parties looks like a status field. It is a balance, a state machine, and a transaction boundary you have to draw narrowly on purpose.
1 min read
Read →13
Eighteen models in TypeScript over SQL, handed over to be moved to a new stack. The rewrite came out with sixteen, which is the number that mattered.
1 min read
Read →14
Letting clients define their own content types means storing schemas as data. That buys instant onboarding and hands back things the database used to do for you.
1 min read
Read →15
What is near me is the query a discovery platform lives on. Where you compute it decides whether the product still works once the catalogue is worth having.
1 min read
Read →