Writing
Observations on software, teams, and craft.
Engineering Level Expectations (SE1–SE4)
A progression framework for software engineers centered on knowing your "One Job" before expanding scope.
Career Progression
A framework for career advancement that decouples compensation from titles and supports multiple paths.
Performance Improvement Plans
When PIPs are appropriate, how to structure them, and what to realistically expect.
Year-End Self-Review Guidance
How to write a self-review that focuses on impact rather than activity, and actually influences your career trajectory.
Engineer Interview Process
A three-stage interview workflow for evaluating software engineers, including guidance on pair programming formats.
Story Card Template
A standard template for defining work scope, acceptance criteria, and technical context.
Ways of Working Template
A living document template for team ceremonies, workflow stages, and operating norms.
One-on-Ones
Cadence and agenda guidance for 1:1s with developers, tech leads, and staff engineers.
Post-Mortem Template
A structured template for incident retrospectives, from detection through action items.
Pairing Guidance
How to run pair programming as a team practice, not a formality — including the anchor rotation model.
Sensible Defaults
Ten engineering organization defaults that raise the baseline for how teams build and ship software.
If you use a spell-book, you might believe its magic.
An observation about developer's growth opportunities