Engineering leadership here means making risk visible: when to freeze production, when to accept accumulated deploy debt, how to run an exception process that does not become political theater, and what to say when a product engineer brings your platform team an idea you do not have room for.
The code-freeze article argues the case from the perspective of the person who had to make the call, not the engineer complaining in Slack. Shipping at Upgrid is the other end of that trade — merge to production in minutes, no holiday freeze — on a small regulated-energy platform. “Say Yes First” is the same problem one level down, inside a platform team. The bootcamp and TDD pieces cover the earlier end of the arc: how you build the judgement these decisions require.
The talks run alongside. DevBCN 2024 covers the path to staff engineer — the same session also ran at WeAreDevelopers and JavaCro that year. The career journeys panel covers non-traditional routes into the work.
Useful if you are a tech lead or EM trying to align teams around constraints that feel arbitrary until you are the one on call.