Ask HN: What are good books/blogs to read for a first time CTO?

Hacker News Discussion ↗

Newly minted CTOs are pointed to a wide range of resources, from classics like *Peopleware*, *The Mythical Man-Month*, and *High Output Management* to newer titles such as *An Elegant Puzzle*, *The Manager’s Path*, and startup-focused works like *The Lean Startup*. Contributors stress that what a CTO should read and do depends heavily on context—tiny startup vs. large org, founder vs. hired exec—with recurring themes of prioritizing product–market fit, business and product understanding, and people/communication skills over deep technical optimization. Many argue that books are most useful as optional guidance, with mentors, peer communities, and direct experience being more valuable for navigating the practical realities and politics of the role.

What “CTO” Means Depends on Context

  • Role varies widely: solo founding engineer, tech lead of a small team, manager of multiple teams, or executive over 100+ engineers.
  • Reading needs change with stage: early-stage “CTO” mostly builds; later-stage focuses on org design, management, and executive decision-making.
  • Some argue early “CTO” is mostly a title/marketing tool until there’s real org scale.

Books and Blogs Commonly Recommended

  • Classic people/management: Peopleware, The Mythical Man-Month, Managing Humans, The Manager’s Path, High Output Management, Scaling People, The Art of Leadership, Managing software teams: the definitive reading list (blog).
  • Engineering leadership/org design: An Elegant Puzzle, The Engineering Executive’s Primer, Accelerate, Team Topologies, Making Work Visible, Think Like a CTO.
  • Startup / product: The Lean Startup, Rework, Inspired, Escaping the Build Trap, The Mom Test, EOS/“Traction” books, Hello, Startup, Game Thinking.
  • Business & general management: The Personal MBA, The First 90 Days, “IT leader” and “IT operations” fables, plus various psychology/systems-thinking titles.
  • Curated lists: GitHub “awesome-cto”, engineering-newsletter and book-list blogs.

Limits of Books; Value of Mentors & Communities

  • Strong theme: books are guidance, not scripture; blindly enforcing playbooks harms morale.
  • Caution against “cargo cult leadership” and leaders who only parrot newsletters.
  • Multiple comments say talking to experienced CTOs and joining communities (CTO lunches, leadership Slacks, CTO groups) is often more valuable than reading.

Startup-Stage Priorities

  • Repeated advice: pre–product-market fit, prioritize building and learning from customers over reading about “being a CTO”.
  • Many advocate extremely scrappy approaches (spreadsheets, no-/low-code, manual ops) until revenue/retention are proven.
  • Warnings about over-investing early in architecture, tooling, and “getting everything right from day one” (survivorship bias called out).

People, Communication, and Leadership Skills

  • Consensus that a CTO spends much of their time on people: communication, negotiation, hiring, developing staff, and navigating politics.
  • Recommendations: communication training (e.g., Dale Carnegie style), exec coaching, psychology/organizational behavior, and “radical candor”-style directness.
  • Emphasis on being transparent about where practices come from, staying humble, and optimizing for the whole business, not just engineering.

Technical Breadth and Depth

  • Many expect a CTO to have enough technical background to evaluate tradeoffs, understand DevOps/architecture/data concerns, and detect nonsense, without necessarily being the top implementer.
  • At very small startups, several argue the CTO should still be coding heavily and expanding across the stack. Others say “learn every technical job” in the company.

Strategy, Business & Product Understanding

  • Several comments highlight strategy, power/politics, and business optimization as core CTO responsibilities at exec level.
  • Advice to learn the company’s domain deeply, industry jargon, and product design/marketing/sales, not just technology.
  • Some note the best execs optimize for company success even when that reduces their own org’s headcount or scope.

Cautions and Meta-Advice

  • Some argue that if someone has to ask “what should I read to be a CTO,” it signals risk; others strongly defend seeking advice as healthy.
  • Multiple reminders that “CTO” at 10-person vs 10,000-person org are fundamentally different jobs; reading choices should match context.