~/series/
Engineering Leadership in 30 Days
30 lessons published · new lesson added daily.
1
Day 1
How AI Coding Tools Shift the Bottleneck to Code Review
2
Day 2
Why Rising Deploy Frequency Can Hide a Real Problem
3
Day 3
Why blockers reach your 1-on-1 late, and how to fix it
4
Day 4
Why corrections don't stick with AI agents between sessions
5
Day 5
Why a metrics-backed promotion slowed my team down
6
Day 6
Why pausing to think beats speed in a coding interview
7
Day 7
Why 'no questions' from a new hire signals broken onboarding
8
Day 8
The fifth team type missing from Team Topologies
9
Day 9
How to make an agent ask instead of guessing
10
Day 10
Why teams don't push back on wrong AI review comments
11
Day 11
How Faster PR Approvals Led to a Rubber-Stamped Bug
12
Day 12
Why Becoming an EM Makes You Worse at First
13
Day 13
Why a promo packet framed as one claim beats a task log
14
Day 14
How to tell a PIP outcome was decided in advance
15
Day 15
Why one postmortem for three audiences ends up too vague to teach
16
Day 16
Why blameless postmortems have no root-cause slot for agent actions
17
Day 17
How to audit who really resolves your on-call incidents
18
Day 18
The Delta Check
19
Day 19
Urgency vs system risk
20
Day 20
Decision Logs
21
Day 21
Contract context files
22
Day 22
Comprehension debt
23
Day 23
Review fatigue
24
Day 24
Motivation in agentic teams
25
Day 25
Conway's Law in reverse
26
Day 26
Span of control and decision load
27
Day 27
The judgment sync
28
Day 28
The swinging door
29
Day 29
Reversal criteria
30
Day 30
Delegating to leaders