Writing

Field notes from
twelve years of shipping mobile.

Notes on stabilizing inherited codebases, rescuing stalled releases, and the judgment calls that separate a real fix from a rewrite — written from the app-rescue work itself, not theory.

The App-Rescue Playbook

The Audit That Found Nothing

Last week a full audit of an Android codebase came back: no verified bugs found. That's either the best sentence in engineering or the most worthless one — and the difference is entirely in the process. Here's the one I run: parallel specialist agents, a failing test before every fix, and a real phone that has to survive a reboot.

Android
Testing
AI-Assisted

July 10, 20266 min read

Read the article

The App-Rescue Playbook
Stabilize Before You Rewrite: An App-Rescue Playbook
Every unstable app I've inherited arrived with the same advice attached: just rewrite it. Here's the five-step playbook I run instead — diagnose, stop the bleeding, add boundaries, fix the pipeline, and only then ask about a rewrite.
July 8, 20266 min read

Field notes fromtwelve years of shipping mobile.

The Audit That Found Nothing

Stabilize Before You Rewrite: An App-Rescue Playbook

Field notes from
twelve years of shipping mobile.