Before you brief anyone

Notes for the person deciding whether to build something, and what to build first. Software development cost, timelines, the trade-offs nobody mentions until the invoice arrives. Nothing here is written for other developers: if a piece cannot help you decide something or ask a better question, it does not get published.

4 articles so far, in four groups: what an internal tool costs and how it is scoped, what changes when the product lives on a phone, how automated tests earn their keep, and what it takes to release and keep something alive. New ones arrive every few days — the schedule is set, so the queue does not depend on anybody remembering.

Deployment and support: what it costs and how long it takes

Deployment and support

Rolling back without making it worse

Every deployment guide says "just roll back". The ones that have actually done it know the hard part is the database, and that the technique has to be practised.

2 min read
Deployment and support

Do you actually need Kubernetes?

It is the default answer to a question most products have not asked yet. Four checks that tell you whether it would earn its keep, from people who chose not to run it.

2 min read
Deployment and support

What it costs to stop deploying by hand

Two weeks and a low four-figure sum buys most small products a pipeline, a tested rollback and alerts that reach a person. Here is what sits in that number and what pushes it up.

2 min read
What we build

Reading rather than deciding? The case studies are the same arguments applied to two real products, with the prices, the timelines and a demo you can open on sample data.