
Organisational Design
Beyond Squads: The Case for Centres of Excellence
When muscles and nerves aren’t enough to stand.
Paved roads that product teams choose on purpose. Golden paths, sensible defaults, release trains, observability that answers questions, and contracts that survive real traffic. Platform as a product, measured by adoption not memos.
Organisational Design
When muscles and nerves aren’t enough to stand.
Developer Experience
Why weekly release trains and a monorepo culture deliver stability, speed, and less toil.
Developer Experience
The case for ringed deployments: safety, visibility, and confidence at scale
Organisational Design
Balancing integration, adoption, and the lure of best-of-breed.
Player Experience
A healthy system creates space to rise, and has the strength to let go.
Developer Experience
The case for a common process supervisor.
Developer Experience
They are canaries. If they go silent, the answer is not to ignore the silence, it is to make the air safe again.
Player Experience
The rise of PWAs and TWAs doesn’t make native redundant — it sharpens its purpose. Native still matters where the web can’t reach: the lock screen, widgets, ecosystem SDKs, and the moments that weave your app into players’ daily lives.
Developer Experience
An orchestra can rehearse in separate rooms. Each section sounds fine to itself. Strings keep time, brass hit their notes. But the first time they come together the rhythms do not match. What was music alone becomes noise together. The only way to avoid it is to rehearse in the
Developer Experience
A player in São Paulo should not feel like a guest in a London lobby. Same skeleton, different clothes. The craft is to let the outfit change without replacing the bones every quarter. Most teams treat localisation as a tidy table of strings, currencies, and date formats. Necessary, yes. Sufficient,