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.
Articles
Notes on iOS engineering and leadership.
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.
Why Hiring for Experienced Engineers Is Broken
Modern hiring systems optimize for risk avoidance and checklist matching, often filtering out the engineers best equipped to deliver long-term impact.
Why Technical Debt Isn’t Debt, It’s Drift
Technical debt can be tracked. Drift cannot. Understanding the difference changes how teams build, refactor, and stay aligned.
The Shift from Senior Engineer to Architecture Leader
What happens when technical mastery stops being enough, and senior engineers begin shaping how teams build, not just what they ship.
The Missing Layer in Most iOS Teams
How architectural leadership, not headcount, separates stable teams from struggling ones.
The 2-Week iOS Codebase Audit: What You Actually Learn
A two-week iOS codebase audit should not be a long report. It should surface real bottlenecks and deliver a plan the team can act on next sprint.