A selected collection of leadership principles, operating models, and real-world lessons from leading web platform teams, improving developer productivity, and partnering with business stakeholders.
I use this playbook to document how I think about engineering leadership: building healthy teams, creating platform leverage, improving execution, adopting AI responsibly, and connecting engineering work to measurable business outcomes.
A web platform is a long-lived product. The choices that compound are editorial experience, who owns maintenance after launch, and whether the architecture stays reusable under pressure.
Speed under pressure is real engineering work. The craft is sequencing so tracks do not block each other, and making every quality-for-speed trade visible and agreed before you take it.
AI tooling sticks when engineers choose it, not when they are told to. Start where the risk is low and the time savings are obvious, keep human review as the guardrail, and measure the difference.
Hiring for how people treat each other, growing engineers into larger roles, and being the steady point when the organization goes uncertain are the same job. Protecting the team is how the work gets delivered.
A weekly one-on-one is a recurring promise to a person, owned by them and protected like any other commitment. Held that way, it stops being a status meeting and becomes the place where trust is built and where friction surfaces long before it reaches the work.