Writing
Notes from
the field
Reflections on engineering leadership, mission software, and the overlooked work that turns code into something people can depend on.
Series
Engineering Manager craft
The Staff→EM bridge: first 90 days, saying no under roadmap pressure, and feedback without politics.
-
2 min read
Performance Feedback Without Politics
Useful feedback is specific, timely, and about observed work — not personality theater. The goal is growth and clarity, not a paper trail built in panic.
-
2 min read
Saying No to Roadmap Pressure Without Losing Trust
Stakeholders do not need unlimited yes. They need engineering partners who make tradeoffs visible early — and keep their word when priorities collide.
-
3 min read
Staff IC to Engineering Manager: What Changes in the First 90 Days
The Staff-to-EM transition is not a promotion into more architecture. It is a shift from being the strongest contributor to building a team that no longer needs you to be.
-
6 min read
What 20 Years Taught Me About Release Governance
Release governance is not bureaucracy. Done well, it is how engineering protects trust — how teams make sure what they build can actually be deployed, supported, reproduced, explained, secured, and operated.
-
2 min read
The Unglamorous Work of Leading Engineering Teams
High-performing teams are rarely the result of a single brilliant hire. They are the product of consistent standards, honest feedback, and the quiet operational work that makes delivery predictable.
-
2 min read
Why Automation Matters More When the Data Is Mission-Critical
In Earth science and disaster-response systems, manual workflows do not just waste time — they delay decisions. Automation is how you turn raw sensor streams into something operational teams can actually use.
Follow along
New essays land here first. Subscribe with your reader of choice — the feed is open and always will be.