Designing a point-of-sale that survives a dead internet connection
Cloud-first POS software fails in the exact moment it matters most: a queue at the counter and no connectivity. Here is how we inverted the assumption.
Read the articleInsights
Notes from building
operating systems.
Architecture decisions, trade-offs and the things that only become obvious once a system is in front of real users. Written by the people who built them, not by a marketing team.
01 / Latest
Three things worth
writing down.
Each piece covers a decision we had to make on a real project, why we made it that way, and what it would have cost to get it wrong.
Why generic billing software loses a finance account's history
Invoicing tools model transactions. Pledge-based lending needs a continuous account. The gap between those two data models is where the money goes missing.
Read the articleWhere the hardware–software boundary actually sits in a robotics programme
Most robotics projects fail at an interface nobody owned. A practical account of which decisions have to be made jointly, and when.
Read the article02 / What gets written here
Specific, not promotional.
We only write about problems we have actually had to solve. Every article names the constraint, the options considered, the choice made and the cost of the alternative — the same way we would explain it to a client's engineering team.
No client data, no identifiable operational detail, and no claim that has not been tested.
Get new pieces
Nothing to subscribe to yet
We have not set up a mailing list, and we would rather not pretend otherwise. If you want to be told when something new goes up, email us and we will add you to a short manual list — no automation, no marketing sequence.
Ask to be notifiedWork with SKI