A backend for five dollars a month: when edge hosting is the right call
The default backend for a new product is a server, a managed database and a bill that starts in the tens of dollars. For many small products, edge functions with an edge database do the same job for a fraction of it. Our game's backend as a worked example, with the numbers, the constraints and when not to do it.
Cloud saves that never lose progress: merge by what a field means
One account on many devices means two devices will eventually be played offline and then sync. Last writer wins deletes progress; taking the maximum of everything duplicates currency. How Kindelve merges a save field by field, according to what each field means.
Build gates: how our website refuses to publish its own mistakes
This site ships in three languages from Markdown and TypeScript, and the mistakes that used to reach production now fail the build instead. The checks we run, from translation parity to accessibility in a real browser, and what they deliberately do not try to do.
The best internal tools start as the spreadsheet everyone is afraid to touch
Every company has a spreadsheet that quietly became a system. It is not the problem to be replaced; it is the specification. How to read it, find what it cannot do, keep what people love about it, and retire it without losing a month of history.
Why every bug fix we ship comes with a test that proves it
Our rule is simple: a bug fix lands with a test that fails without the fix. How we apply it, how we make it hard to skip without making it impossible, and why it is the cheapest quality practice we know.
Building integrations that survive the vendor's next API change
The integration worked the day it shipped. Eight months later it quietly stopped, because a vendor renamed a field. Seven habits that make an integration between two systems survive the changes neither side warns you about.
How to scope a custom software project so it actually ships
Custom software projects rarely fail in the code. They fail in the scope: too large to finish before the priorities change. How we write the job down, find the smallest release worth having, and keep a list of what we are not building.