Soft Skills & Ecosystem Deep Dive · 4 of 12

Time & Focus — Protect the Hours That Matter

Real engineering happens in 90-minute uninterrupted blocks. Email, Slack, and "got a sec?" are the natural enemies. The senior engineers who out-ship everyone aren't smarter — they're better at saying no, batching shallow work, and treating their calendar like production infrastructure.

Deep workMaker vs ManagerYak-shavingWIP limitsFocus blocks
← Back to Soft Skills & Ecosystem
Maker vs Manager

Two Different Calendars

Paul Graham's classic essay: managers run on hour blocks, makers on half-day blocks. A meeting that costs a manager 60 minutes can cost a maker an entire afternoon. The fix is structural, not heroic — defend mornings, batch meetings, and tell people you're doing it.

  • No-meeting mornings — protected calendar block; everyone learns to schedule afternoons.
  • Office-hours blocks for ad-hoc questions instead of constant interrupts.
  • Async-by-default updates so meetings stop being for status.
  • Meeting-free days (Wednesdays at many shops) — sacred to most teams that try them.
Deep Work Habits

What Actually Works

  • Single-task. Multi-tasking is task-switching. Each switch costs ~15 minutes of recovery.
  • Notifications off. Batched email + Slack three times a day; nobody dies.
  • One personal WIP item at a time. Two becomes none.
  • Pomodoros — 25/5 cycles work for some; 90/20 fits maker brain better.
  • Plan tomorrow today. Write down the first thing to do; arrive without decision fatigue.
  • Energy > hours. Two great hours of focused work beats six tired hours.
  • Sleep is engineering practice. Tired people write bugs; bugs cost more than the meeting they skipped.
The Trap

Yak-Shaving

"I need to ship a feature → first I need to upgrade the build → first I need to update the framework → first I need to debug the new linter → first I need to set up a new toolchain..." Three days later you've shaved an entire yak and shipped nothing.

  • Time-box detours. "If I can't fix this in 30 minutes, I do the workaround and file a ticket."
  • Distinguish yak-shaving from real work. Sometimes the build does need fixing — but is it your job today?
  • Park the urge. Capture every "wait, while I'm here..." in a list; come back later.
  • Branch off main. Random improvements to the toolchain stay isolated from the actual feature.
Saying No

The Hardest Skill

  • "Yes, after X." Honest commitment, not infinite queue.
  • "Help me prioritize this against Y." Forces the requester to own the trade-off.
  • "That's a great idea — let's add it to the backlog." Polite filtering; track and triage.
  • "I'm not the right person." Direct people to the actual owner.
  • "Not this quarter." Real, useful, calibrated pushback.
Tradeoffs

Pitfalls

  • Defending too much. Hermits don't get promoted. Be available; just not all the time.
  • Tool fetishism. Switching note-taking apps is not productivity.
  • Ignoring the team. Your focus shouldn't make others wait days for unblocking.
  • Crunch as default. Long hours signal poor planning, not heroism.
  • Burnout creeps. Watch for the symptoms in yourself; nobody else will.
Continue

Other Soft Skills