Writing — All articles
Writing
I write when something I've built, broken, or had to maintain for years turns out to be worth explaining. Mostly architecture, debugging, and the decisions whose cost only shows up later.
The Error Message Was Lying
A Salesforce JWT auth failure that had nothing to do with JWT, Salesforce, or auth. On reading errors as evidence rather than instructions.
Errors are evidence, not instructions. They tell you where the failure surfaced, and almost never where it started.Read
Permissions Are Architecture, Not a Feature
Every system that gets permissions late pays for it twice. Notes from nine years maintaining a four-layer permissions model.
A permissions model is not a check you add at the top of a handler. It is a claim about what every query in the system is allowed to return.Read
In Offline-First Apps, Sync Is the Product
Building a field platform that had to work with no signal taught me that the UI is the easy half — and that sync bugs never announce themselves.
The moment a device can accept a write without reaching the server, you have two copies of the truth that are permitted to disagree.Read
3 articles · Debugging, OAuth, Production, Architecture, Permissions, Systems
Tell me what's breaking.
A system that needs building, an integration nobody on the team wants to touch, or a technical decision you'd like a senior second opinion on before you commit. I take on a limited number of engagements at a time, so I can usually tell you within a day or two whether it's a fit.
Get in touch