Growing your career
Productivity, focus and sustainability
Leverage, deep work, saying no, and a pace you can still think clearly at in year five.
Engineering careers are not won by who sits at the keyboard longest. They are won by who repeatedly puts hours into work with outsized leverage — and who can still think clearly in year five. Busy calendars, always-on Slack, and heroic late nights feel productive while quietly destroying the conditions for hard technical judgment.
The operating system is small: prioritize by leverage, protect focus, invest in tools that compound, decline work without drama, and notice burnout before it becomes a forced exit. Start the week by naming three high-leverage outcomes and protecting time for them first. Measure focus in uninterrupted blocks, not hours online.
A week that works looks ordinary. Monday you name three outcomes — ship the design, decide the API, cut a noisy alert — and put 90-minute blocks on the calendar before anyone else claims them. You batch Slack twice a day. You automate the log dance you have done four times. You say "after Thursday, or Priya owns this" instead of a vague yes. You treat a week of no evenings off-call as a page on you, not a badge. None of that is a personality transplant. It is a few defaults you repeat until they are boring.
Concepts in this section
Read them in order.
| Step | Concept | What it answers |
|---|---|---|
| 1 | Engineering leverage | What is the highest-impact use of the next hour? |
| 2 | Protecting focus time | How do you keep chunks for hard thinking? |
| 3 | Tooling and automation | Which skills compound for years? |
| 4 | Saying no | How do you decline without drama? |
| 5 | Sustainable pace | What does burnout look like, and what actually fixes it? |
Leverage assumes a working brain. Sleep debt and "I'll rest after this launch" destroy the numerator even when the calendar looks disciplined. You cannot compound hours you no longer have. Put hard thinking in your peak hours. Budget about 10 hours of meetings a week as an IC default, and convert anything without a decision to a doc. After a launch or incident week, put recovery on the calendar before the next push. That is delivery, not a side quest.
Common mistakes
- Optimizing for busyness. Motion is not the numerator.
- Heroics as a plan. Calibration forgets them. Your nervous system does not.
- A calendar owned entirely by other people. Raise it with data in a 1:1.
Key takeaways
- Optimize for leverage, not hours.
- Protect maker focus; batch communication and meetings.
- Tooling compounds; saying no is how high-leverage work survives.
- Sustainability is a performance feature. Burnout destroys judgment.
Further learning
Edmond Lau's Talks at Google session is the best single video on engineering leverage.
MIT Missing Semester Lecture 1 (shell):
The Missing Semester of Your CS Education (MIT)Master powerful tools that will make you a more productive computer scientist and programmer.Missing Semester
Related
Growing your scope
From tasks to features to projects to problems: finding and taking on higher-leverage work.
Ownership
Acting like an owner: close loops, care about outcomes, and be the person things do not fall through with.
Career strategy
Choosing companies, teams and specialties deliberately: big tech vs startups, generalist vs specialist.