The Future Needed a Top-Up
The model could change its mind. I still had to deal with the permissions, the tests, and the sofa refund.
Articles
Notes on iOS engineering and leadership.
Do You Really Need to Synchronize That State?
The ordering bug began before the actor. Fixing it eventually put registration and completion on the same stream, leaving the registry with one owner.
When the Architecture Survives the Rewrite
Reusing an architecture turned out to mean replacing most of its machinery and discovering which parts had actually been architecture all along.
After the Friction Disappears
Productivity breakthroughs remove old constraints, then expose the work required to keep independently moving parts aligned.
Why AI-First Roles Feel Surprisingly Familiar
AI changes the economics of production. It does not eliminate the need for coherence.
Why DI Becomes a Liability at Scale
Dependency injection helps early, but at scale it can preserve coupling instead of preventing it. The real issue is not wiring, it is boundaries.
When Boundaries Change How a Team Works
Clear architectural boundaries do more than organize code. They change onboarding, code review, delivery rhythm, and how teams think about ownership.
Independent Components Without Deep DI
A scoped message channel can keep components independent without turning your app into a global event bus, as long as orchestration and state mutation stay centralized.
A Boundary-First Structure That Stays Small
A small set of boundaries that keep an iOS codebase loose: AppContext orchestrates, AppServices do work, AppState stays value-only, and ViewContext becomes the view’s contract.
When iOS Architectures Start Fighting Back
How small boundary violations compound over time, and why many iOS codebases begin to resist the very teams trying to evolve them.