Skip to content

Instantly share code, notes, and snippets.

@KevinT
Last active November 14, 2020 12:27
Show Gist options
  • Save KevinT/c5970a7831e3a4ff53d76d832f9eb9b9 to your computer and use it in GitHub Desktop.
Save KevinT/c5970a7831e3a4ff53d76d832f9eb9b9 to your computer and use it in GitHub Desktop.

Question posted on Twitter

For someone with technical leadership responsibilities in a rapidly scaling product company that’s distributed across multiple time zones, what are the top 3 books you think they should read?

My Three

  1. Flow (Donald G. Reinertsen)
  2. Flow (Mihaly Csikszentmihalyi)
  3. Flow (Nonaka, Toyama, Hirata)

Twitterverse

  1. Blitzscaling (Ried Hoffman)
  2. Deep Work (Cal Newport)
  3. Drive (Dan Pink)
  4. Extreme Ownership
  5. Founders at work
  6. Hard facts, dangerous half-truths & total nonsense (Pfeffer & Sutton)
  7. Hard things about hard things
  8. Leadership and Self Deception (The Arbinger Institute)
  9. Remote (37 Signals)
  10. Scaling Lean & Agile Development (Larman, Vodde (+other books by these authors))
  11. Scaling up Excellence (Sutton and Rao)
  12. Software Architecture for Developers vol 1 & 2 (Simon Brown)
  13. Teaming (Amy Edmonson)
  14. The Anatomy of Peace
  15. The business of Belief (Tom Asacker)
  16. The Culture Code (Coyle)
  17. The fifth discipline (Peter Senge)
  18. The Lean Startup (Eric Ries)
  19. Thinking in Systems (Donella Meadows)
  20. Wardley Maps (Simon Wardley (not a book))
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment