Chaos and Order

💡 왼쪽 원문을 읽으면서 오른쪽에 따라 써보세요. Tab 키로 힌트를 받을 수 있습니다.

Intro — "Worked 10 hours, wrote 100 lines — why?"

Almost every developer knows the feeling. Causes:

10–15 hours/week meetings
5–10 hours/week Slack/Email
Context switching (studies: interrupted every ~4 minutes)
Daytime fog from burnout
Only quiet late at night → health collapse

This post covers:

Deep Work — Cal Newport, put into practice
GTD — David Allen adapted for developers
Calendar Blocking, Time-boxing, Pomodoro compared
Meeting, Slack, Email triage
Manager vs Maker schedule
Burnout early signs and prevention
Staying sharp in your 40s and 50s

Season 3 Episode 9. Last time, in "Finances," we said time compounds. This post is how to spend it.

Chapter 1: Deep Work — Why Depth Matters

1.1 Definition

Cal Newport (Deep Work, 2016):

"Deep Work: Professional activities performed in a state of distraction-free concentration that push your cognitive capabilities to their limit. These efforts create new value, improve your skill, and are hard to replicate."

The opposite is Shallow Work: logistics, email, meetings, repetitive tasks.

The modern knowledge-work trap: Shallow expands, Deep shrinks.

1.2 Why Developers Need It

Complex debugging, architecture design, learning new tech — all Deep Work.

1 hour Deep > 5 hours Shallow. Quality of focus beats quantity.

1.3 Four Modes of Deep Work

Monastic: Block all shallow. Why Knuth lives without email.

Bimodal: Alternate long monastic stretches with shallow. Example: two-week focus sprints while writing a paper.

Rhythmic: Same block every day (e.g. 6–9 AM).

Journalistic: Snatch Deep Work whenever possible. Requires practice.

1.4 Building the Environment

Block scheduling: protect Deep Work slots on the calendar
Notifications off: Do Not Disturb, Slack Snooze
Physical separation: meeting room, cafe, library
Start ritual: coffee, music, code
End ritual: declare "done for today"

1.5 Daily Ceiling

Beginner: 1–2 hours/day
Trained: 3–4 hours/day
Ceiling: ~4 hours/day (Newport, Knuth)

You cannot do 8 hours of Deep Work. It is four sprints, not a marathon.

Chapter 2: GTD — Emptying the Mind

2.1 Five Stages

David Allen (Getting Things Done, 2001):

Capture — move everything out of your head
Clarify — decide what it means
Organize — sort by category
Reflect — regular review
Engage — pick what to do now

2.2 Capture Tools

Paper notes, apps (Notion, Apple Notes, Obsidian)
Single inbox: everything flows into one place
"Inbox Zero" is unrealistic; "regular drain" is realistic

2.3 The Two-Minute Rule

Clarify stage:

"If it takes less than two minutes, do it now."

Short email replies
Tiny PR reviews
Adding code comments

Reason: the cost of storing and tracking exceeds the cost of doing.

2.4 Contexts

Group tasks by where/how:

@computer — needs a computer
@phone — needs a call
@office — needs the office
@waiting — waiting on someone
@someday — someday/maybe

Developer variants:

@code — at the IDE
@review — PR review
@design — docs/diagrams
@meeting — meeting prep
@learn — books/courses

2.5 Weekly Review

30–60 minutes once a week:

Drain the inbox
Review active projects
Pick top 3 for next week
Update the Someday list

Without this, GTD falls apart.

2.6 Developer Adaptation

Capture:

Slack alerts → Todoist/Notion
Bugs → Jira/Linear
Ideas → Obsidian daily note

Clarify/Organize:

Jira backlog = long-term store
Todoist = this week / today
Calendar = blocked work

Engage:

3 priorities today (MIT — Most Important Tasks)
Fixed time on the calendar

Chapter 3: Calendar Blocking

3.1 Definition

Assign every hour of the day to a block. Decide up front what happens when.

3.2 A Developer Day

08:00 - 09:00  Morning routine + exercise
09:00 - 11:30  Deep Work: core coding
11:30 - 12:00  Slack/Email triage
12:00 - 13:00  Lunch + reading
13:00 - 14:00  Meeting (weekly sync)
14:00 - 15:00  PR review
15:00 - 17:00  Deep Work: second block
17:00 - 18:00  1-on-1 / wrap-up
18:00+         Personal time

3.3 Buffer Rules

15-minute buffer between meetings — travel, breathe, prep
30-minute buffer between blocks — cognitive switch
1.5x time — if you expect 1 hour, block 1.5

3.4 Protecting the Block

Label it "Focus Time"
If someone accepts-but-overrides, ask to move
Share Slack/Zoom status: do not disturb

Google Calendar's Focus Time feature auto-declines and suppresses Slack alerts.

3.5 Obstacles

Urgent incidents: they will eat blocks. Reserve slack capacity.
Manager meetings: hard to refuse. Pre-register focus blocks.
Your own urges: Slack cravings. Block the app.

Chapter 4: Time-boxing

4.1 vs Calendar Blocking

Calendar Blocking assigns time to tasks. Time-boxing assigns a limit to each task (stricter).

4.2 Examples

Review this PR → 30 min
New feature spike → 4 hours (if over, rethink approach)
Investigate this bug → 2 hours (after that, escalate)

4.3 Parkinson's Law

"Work expands to fill the time available."

No limit → infinite polishing. Limit set → priorities forced.

4.4 Practical Rules

Stuck for 2 hours → ask a colleague
4-hour spike → change the approach
30-minute meeting → do not exceed 30 minutes

Chapter 5: Pomodoro and the Ultradian Rhythm

5.1 Pomodoro

25 minutes focus + 5 minutes break
4 rounds then a long break (15–30 min)
Francesco Cirillo, 1980s

Pros: simple, easy to start. Cons: 25 minutes may cut flow right when it starts.

5.2 90-Minute Ultradian Rhythm

Natural human cycle = 90 min focus + 20 min rest
Peter Schulman, Nathan Kleitman research
Better suited to developer Deep Work

5.3 Flow State

Mihaly Csikszentmihalyi:

Challenge ~ matches skill
Clear goals
Immediate feedback
Loss of time awareness
Loss of self

15–20 minutes to enter. A 25-minute Pomodoro never hits flow.

5.4 Recommendations

Complex coding: 90-minute block + 20-minute break
Simple PR review: 25-minute Pomodoro
Learning/reading: 45–60 minutes

Chapter 6: Manager vs Maker Schedule

6.1 Paul Graham's Essay

Paul Graham (2009):

Manager's Schedule: one-hour slots. Meetings are default.

Maker's Schedule: 2–4 half-day blocks. A single meeting destroys a block.

Developers are makers. One morning meeting = morning Deep Work lost.

6.2 Clash and Fix

Manager:

"30-minute meeting at 10?"
From manager's view: seven hours left till 2 PM
From maker's view: morning block destroyed

Fixes:

Cluster meetings in the afternoon
Declare "no meetings in the morning"
Replace with async (recorded video, docs)

6.3 "No Meeting Day" Culture

Many companies adopt it. Examples:

GitLab: Focus Friday
Asana: Wednesday No Meeting
Basecamp: minimal meetings by design

6.4 Staff+ Shift

Up to Senior, mostly Maker. Once Staff+, Manager duties grow.

Compromise:

Morning: Maker (Deep Work)
Afternoon: Manager (1-on-1, reviews, meetings)

Chapter 7: Slack, Email, and Meeting Triage

7.1 Slack Rules

As a sender:

Use threads (keep channels clean)
Finish thought in one message
Do not spam @here, @channel
Prefer channels over DMs (knowledge sharing)

As a receiver:

Use DND (Do Not Disturb)
Silence during focus blocks
Open Slack at set times only (10:00, 13:00, 16:00)
Notifications on mobile only (desktop stays quiet)

7.2 Email Triage

Daily Inbox Zero:

Delete (spam, newsletters)
Reply (under 2 minutes)
Delegate (their job)
Defer (add to todo)
Archive (reference)

Time cap: 15 min morning, 10 min noon, 10 min evening.

7.3 Meeting Triage

Accept if:

You are a decider
Pre-read material exists
Purpose is clear
No other slot available

Decline script:

"Thanks. If you can move forward without me, please share notes. Otherwise could we try next week?"

7.4 Fewer Meetings

Sync → Async: Loom, rolling doc
Review recurrings quarterly: kill what is stale
Standup alternative: Slack daily post

Chapter 8: Burnout — Early Signs and Prevention

8.1 WHO Three Factors

Emotional exhaustion — drained, depleted
Depersonalization — "nothing matters"
Reduced accomplishment — feeling ineffective

8.2 10 Early Signs

Hard to get out of bed
No interest in meetings
Dread of Slack (even weekends)
Disproportionate anger at small bugs
Coworkers' words grate on you
Weekends no longer recover you
Sleep quality drops
Eating/drinking rises
Exercise stops
Hobbies feel dull

8.3 Prevention

Daily:

7–8 hours sleep
30+ minutes exercise
Real lunch break (not coding)
Kill Slack in the evening

Weekly:

One full day of the weekend off work
Family/friend time
Nature (walk, park)

Yearly:

Use all PTO
One stretch of 1+ weeks off (brain needs ~10 days to reset)
Sabbatical if needed

8.4 Recovery

Early:

Take a week off
Restore exercise, sleep
Cut meetings in half

Middle:

Change role/project
Consider therapy
Team reshuffle

Late:

Look for a new job
Sabbatical or part-time
Psychiatric help

Chapter 9: Staying Sharp in Your 40s and 50s

9.1 Reality of Aging

Working memory declines from late 30s
Learning new tech takes longer
Recovery is slower

9.2 Strategies

Fitness:

3x/week cardio (heart = brain)
Strength training (sarcopenia starts in the 40s)
Stretching (lower back, neck)

Diet:

Mediterranean-style (olive oil, fish, vegetables)
Protein at breakfast (brain fuel)
Hydration, electrolytes

Sleep:

7–9 hours
Manage blue light
Sleep-tracking apps

9.3 Strength of Experience

Aging is not pure loss:

Judgment: pattern-match across cases
Decisions: fast and accurate
Communication: calm, persuasive

For Staff+ engineers, experience is the weapon.

9.4 Long-Lived Developers

Small daily learning beats binge learning
Sustained curiosity: new languages, new domains
Network: stay connected to younger peers
Simple life: sustainability over flash
Let go of ego: pride drops a lot past 40

Chapter 10: Time Management While Remote

10.1 Upsides and Traps

Upsides: zero commute, focus, family. Traps: blurred boundaries, isolation, less movement.

10.2 Rituals of Separation

Morning ritual: change clothes, coffee, a walk, then desk
Evening ritual: close laptop, a clear "clock out" step
Workspace split: do not work from the bedroom

10.3 Avoiding Isolation

Out of the house 1x/week (cafe, coworking)
Offline meetup 1x/week (community, friends)
Family/friend call 1x/week

10.4 Async Culture

Not everything goes into Slack (docs)
Loom (3-minute recording = 30-minute meeting)
Daily Slack post instead of standup
Decision Log as documents

Chapter 11: Tool Recommendations

11.1 Task Managers

Todoist: simple, cross-platform
Things 3: Apple ecosystem, beautiful
OmniFocus: GTD specialist
Notion: flexible
Linear/Jira: work

11.2 Notes

Obsidian: Markdown, local, Zettelkasten
Apple Notes: basic but strong
Notion: DB + notes
Roam Research: bidirectional links
LogSeq: open-source Roam

11.3 Focus Tools

Freedom: site blocker
Cold Turkey: forceful blocker
Focus To-Do: Pomodoro
macOS Focus Mode: built-in and strong

11.4 Calendar

Google Calendar: default
Fantastical: natural language input
Cron/Notion Calendar: modern UI

11.5 AI Assistants

ChatGPT/Claude: brainstorming
Notion AI: note summaries
Raycast AI: quick queries
Copilot (Writer, Code): repetitive work

Chapter 12: 12-Item Productivity Checklist

Chapter 13: 10 Productivity Anti-Patterns

1) "Look Busy" Theater

Fast Slack replies to perform busyness. No real value. Visibility is not productivity.

2) Bragging About Multitasking

Three things at once. Context-switching cost 40%+. Single-task.

3) All Notifications On

Every app interrupts hundreds of times a day. Default OFF.

4) Meetings Feel Like Productivity

Eight hours of meetings = eight hours of output? Nothing got built.

5) "I Will Rest Later"

Rest after the project. Projects never end. Regular rest is non-negotiable.

6) Caffeine Abuse

4+ cups of coffee. Sleep ruined, anxiety up. None after 2 PM.

7) Late-Night Catch-Up

Meetings by day, code by night. Sleep destroyed. Defend Deep Work in daylight.

8) Chasing the Perfect Setup

Hours tuning Notion / Todoist. No real work. Ship at 80% setup.

9) "I Do Not Need Manuals"

Scorn checklists, repeat the same mistake. Checklists are professional.

10) Cannot Rest

Slack even on holiday. Rest is a skill. Practice it.

Closing — Time Is the Only Finite Resource

Principle 1: Productivity Grows From Health

Sleep, exercise, diet are the foundation. Any system fails without them.

Principle 2: Simple Beats Fancy

30 Notion templates < one page of notes + one todo. Simple beats polished.

Principle 3: Design the Day in Advance

Pick 3 MITs in the morning. Review at night. Those two moments are the core.

Principle 4: "No" Makes "Yes" Possible

Without refusal, no focus. Shield yourself from the unimportant.

Principle 5: Consistency Beats Perfection

A little every day beats a binge. Compounding wins.

Principle 6: Read the Originals

Next — "Developer Mental Health Complete Guide"

Season 3 Ep 10 will cover:

Developer mental health statistics (Stack Overflow Survey)
Impostor syndrome mechanics
Managing anxiety and stress
Early signs of depression
Therapy, CBT, meditation
Company EAP programs
Why Korean developers hesitate with psychiatry
Community and peers
Family support, or barriers
Recovery and relapse prevention

See you there.