Sabbaticals and Burnout Recovery for Engineers: Rest as a System, Not a Weekend
Leave policies, coverage plans, and coming back without picking up the pager on day one — treating recovery like an incident with a timeline.
Tag
16 articles · 60 min of reading
Leave policies, coverage plans, and coming back without picking up the pager on day one — treating recovery like an incident with a timeline.
Rubrics, work-sample questions, and calibrated no-hires: how to run a loop that candidates experience as fair and the company can defend.
A lightweight IC / comms / ops split you can run at 2am, what to write in the first fifteen minutes, and how to hand off without dropping context.
Lead time, deploy frequency, change fail rate, and time to restore — how to collect them honestly, and how teams game the dashboard.
Why software estimates are systematically wrong in the same direction, and the practices that produce more useful forecasts than a single number ever could.
How Amazon's two-pizza teams, operational readiness reviews, and correction-of-error documents work together as an operating system, not just slogans.
Why undocumented architectural decisions get relitigated endlessly, and how a lightweight ADR practice preserves the reasoning without becoming bureaucratic.
A practical framework for the first 90 days on a new engineering team, from mapping the codebase to earning trust before shipping big changes.
Inside Amazon's PR/FAQ process, where teams write a mock press release and FAQ before writing code, and why engineers treat it as a real design tool.
How trunk-based development and merge queues reduce integration pain compared to long-lived feature branches, and what they require to work in practice.
Why most postmortems produce a document nobody acts on, and what separates a blameless postmortem process that genuinely prevents repeat incidents.
How to write code review comments that engineers actually act on, without triggering defensiveness or turning review into a status contest.
Why Spotify organized engineering around autonomous squads instead of functional teams, and what the model got right and wrong as the company scaled.
Design docs stall for predictable reasons — missing context, buried trade-offs, no clear ask — and each one has a specific, fixable cause.
Mentorship advice usually addresses only one side of the relationship — the skills that make it work are different depending on which seat you're in.
Seniority shows up less in what someone knows and more in a handful of repeatable habits around scope, communication, and how they handle being wrong.