Books That Helped Me Become a Tech Lead

Abstraction: Curated book list for senior engineer to tech lead transition

Key points:

• "Design It!" (Keeling): key lesson — "no design" means multiple implicit, unaligned designs; design explicitly, collaboratively, and document it
• "Release It!" (Nygard): production reliability patterns and antipatterns; engineers must design for production from day one
• "Site Reliability Engineering" (Google/Beyer et al.): SLOs and error budgets as tools to make explicit reliability-vs-velocity tradeoffs
• "Thinking, Fast and Slow" (Kahneman): System 1 (fast/intuitive) vs System 2 (slow/deliberate) thinking; awareness of cognitive biases
• "Atomic Habits" (Clear): small incremental habit changes compound into large productivity gains; focus on systems over goals
• "First, Break All the Rules" (Buckingham/Coffman): best managers focus on employees' strengths, not fixing weaknesses

Connections: Software Architecture · Tech Leadership · Software Engineering

Source: https://dev.to/frosnerd/books-that-helped-me-become-a-tech-lead-3831