Articles
Plain-English articles on getting work off your plate.
What we’ve learned building software people rely on: when to automate, where things should run, and how to make systems that keep working when a piece of them fails.
- When a spreadsheet should become an appSpreadsheets are brilliant until they quietly become the system your business runs on. Six signs it’s time, and what to keep when you move.
- Self-hosted, cloud or on-device: where software should runWhere a piece of software runs shapes its cost, its privacy and what happens when the internet drops. How we choose, with three real examples.
- Software that fails gracefullyEvery system breaks somewhere. The good ones keep working when a piece fails. Four habits we build in, and where they’ve saved the day.
- Let the server be the refereeWhat multiplayer games taught us about business software: check every rule where nobody can tamper with it, and send people only what they may see.
Next step
What’s the job you’d like to stop doing by hand?
Describe the problem in a few sentences. Within one working day you’ll hear whether software would fix it, roughly what it would take, and what we’d look at first.