What we have learned shipping this.
Notes from building and running platforms in payments, healthcare and logistics. Written by the engineers on those platforms.
Editorial standard
What gets published.
Written by engineers
Pieces are written by the people who did the work. A marketing team can produce more articles per month and none of them will tell you anything you could act on.
Specific or not published
An article has to contain something we would have wanted to know a year earlier. General advice about digital transformation is not a shortage anyone is suffering from.
Including the things that went wrong
The useful half of any engineering write-up is the part where the first approach failed. That part stays in.
Articles
Three pieces, from one platform.
All three come out of the same engagement, which is why they are specific. More follow as the work produces something worth writing down.
October 10, 20265 min readThe address, not the phone number
A finished form, a morning at the counter, and nine findings that shipped in one release.
Read it
October 10, 20266 min readA design system is mostly a deletion project
Two token files, sixteen documented components, and the unglamorous part nobody budgets for.
Read it
October 10, 20265 min readProof of delivery is a dispute-resolution feature
A signature is not proof. What a delivery record needs to carry to end an argument.
Read itStart a conversation
Tell us what you are trying to ship.
You will get a reply from an engineer, not a form handler. If we are not the right firm for it, we will say so and tell you who is.