Free CTO Resources: Best Books, Podcasts & Communities

The best free resources for CTOs and aspiring CTOs are practitioner-written blogs and newsletters (Will Larson's Irrational Exuberance, The Pragmatic Engineer, LeadDev), free communities (Rands Leadership Slack, CTO Craft), the DORA research programme, and a short list of books you buy once. Pick one resource per gap rather than collecting everything.

The challenge is not scarcity. It is curation. There are thousands of blog posts, hundreds of podcasts, dozens of communities and more books than anyone has time to read. This guide lists the resources worth your time, organised by format, and links each one to its official page. We checked every link in October 2026; formats, prices and membership rules change, so confirm before you commit.

What are the best free CTO resources at a glance?

The table groups the resources by what they cost and what they are best for. "Free" means free to read, listen to or join at the time we checked. Books are paid purchases and are marked as such.

Which books are worth buying for CTOs?

Seven books cover most of the ground: The Manager's Path, An Elegant Puzzle, Staff Engineer, High Output Management, The Hard Thing About Hard Things, Accelerate and Team Topologies. They are not free, but each is a one-time purchase that repays re-reading as your role changes. If you can only buy one, start with the one that matches your current stage.

The Manager's Path by Camille Fournier

The publisher describes the book as a guide for each stage in the journey from engineer to technical manager, with a late chapter on senior leadership that covers the VP of Engineering and CTO roles. It gives you language for transitions you are living through but cannot yet articulate. If you read one book on this list, read this one.

To see the same progression mapped to courses and programmes, our guide to engineering manager courses and the development pipeline by stage covers each stage.

An Elegant Puzzle by Will Larson

Larson's book, published by Stripe Press in 2019, is about systems of engineering management. It suits directors and VPs who run the engineering function rather than a single team. Larson's blog (below) is the free companion to it.

Staff Engineer by Will Larson

The book is about leadership beyond the management track. According to the StaffEng.com FAQ, most of its writing is available free on the site, which lists guides such as staff engineer archetypes and promotion packets, alongside interviews with staff-plus engineers. Relevant for CTOs because many CTOs left the IC ladder early and need to build one.

High Output Management by Andrew Grove

Grove was Intel's chief executive and writes for managers at every level, not only executives. The paperback dates from 1995. It treats management as a set of activities with leverage, which is the right lens for a first-time CTO who still thinks in terms of individual output.

The Hard Thing About Hard Things by Ben Horowitz

Horowitz draws on his time as CEO of Opsware, which Hewlett-Packard acquired in 2007. The a16z page describes chapters on difficult decisions such as demoting or firing a friend and managing your own mindset as a leader. It suits startup CTOs for the same reason: the choices rarely have a clean answer.

Accelerate by Nicole Forsgren, Jez Humble and Gene Kim

The book reports four years of research, including State of DevOps data, on how to measure software delivery performance and what drives it. It is the background to the DORA metrics discussed below, and gives you evidence when you need to justify engineering practices to a non-technical board.

Team Topologies by Matthew Skelton and Manuel Pais

The authors' model is based on four fundamental team types and three team interaction patterns. It is useful for CTOs and VPs responsible for organisation design, because it ties team structure to the flow of change rather than to copying another company's org chart. See also our guide to scaling your engineering organisation.

Which podcasts are worth your time?

Podcasts work for dead time such as commutes and walks. Three are worth following for CTOs: Software Engineering Daily for technical breadth, Lenny's Podcast for product leadership, and the Engineering Leadership Community's podcast for leader interviews. Treat them as supplements to reading, not substitutes.

• Software Engineering Daily. An independent podcast running since 2015 with free episodes. Its topics include AI and machine learning, architecture, cloud, distributed systems, data, security and careers. Useful for maintaining the technical breadth you need to make strategic bets.
• Lenny's Podcast. Covers product, career and growth. Not engineering-specific, but CTOs who work closely with product benefit from the perspective.
• Engineering Leadership Community podcast. The community lists a podcast of interviews with engineering leaders alongside its events and peer groups.

What are the best communities for CTOs and VPs of Engineering?

The best-known communities for engineering leaders are Rands Leadership Slack, CTO Craft, the Engineering Leadership Community and LeadDev's community. Rands is free and run on invitation by email; CTO Craft is aimed at CTOs and senior technology leaders and has a free community tier. Join one, participate in it, and add a second only after a few months.

How to choose. If your main need is peer advice on a specific management problem, start with Rands Leadership Slack. If you are already a CTO or VP and want peers in the same role, start with CTO Craft. If you want a small recurring group with accountability, look at the Engineering Leadership Community's peer groups.

Hacker News is not a leadership community, but the technology discussions are a useful read on how practitioners think. Its culture can be abrasive, so use it for technical perspective rather than management advice.

If you want a paid, structured alternative to a community, see our CTO coaching directory, our comparison of coaching, training and mentoring and CTO mentor programs compared.

Where do VPs of Engineering go to network in person?

VPs of Engineering mostly meet peers at LeadDev's conferences, CTO Craft's events and the Engineering Leadership Community's annual conference and local events. As of October 2026, LeadDev's site lists conferences in New York (September 2026), Berlin (November 2026) and London (June 2027), CTO Craft lists events in Amsterdam, Stockholm and London, and the ELC Annual conference runs 13 and 14 October 2026 in San Francisco.

Dates and locations change every year, so confirm on each organiser's page: LeadDev, CTO Craft and ELC.

Newsletters and blogs

Written content allows depth that other formats cannot match. These are the consistently useful ones.

• Irrational Exuberance by Will Larson. Posts on engineering leadership, strategy, staff-level careers, hiring, developer productivity and architecture. Larson's books listed on the site include An Elegant Puzzle, Staff Engineer, The Engineering Executive's Primer and Crafting Engineering Strategy.
• The Pragmatic Engineer by Gergely Orosz. Covers big tech and startups from the inside, aimed at software engineers and engineering leaders.
• LeadDev. Free articles, videos, research reports and newsletters organised by topic such as management, culture and hiring.
• Lara Hogan. An author and coach for managers and leaders. Her blog covers one-on-ones, feedback, hiring, influence and leading through crises.
• charity.wtf by Charity Majors. A Substack on observability and tech advice.
• The Engineering Manager by James Stanier. Articles on engineering management, organised into Management 101, Growth and Managing managers.
• StaffEng.com. Guides and interviews on staff-plus engineering, free on the site.

Free tools and frameworks

DORA metrics (dora.dev)

Google's research programme on software delivery performance. DORA's current model has five metrics: change lead time, deployment frequency and failed deployment recovery time (the throughput measures), and change fail rate and deployment rework rate (the instability measures). Failed deployment recovery time replaced mean time to restore in the current model (DORA). Older articles, and some books, still describe the original four keys.

Westrum organisational culture model

Ron Westrum's typology sorts organisations by how they handle information: pathological (power-oriented), bureaucratic (rule-oriented) and generative (performance-oriented). DORA's research finds that a high-trust, generative culture predicts software delivery and organisational performance (DORA, generative organizational culture).

Architecture decision records

Not a resource but a practice. Michael Nygard's original template has five sections: title, context, decision, status and consequences. They are free to adopt and preserve the reasoning behind decisions after the people involved have moved on (Nygard, 2011).

Thoughtworks Technology Radar

Published twice a year, the Technology Radar is an opinionated snapshot of tools, techniques, platforms, languages and frameworks. Its rings are Adopt, Trial, Assess and Caution. Volume 34 appeared in April 2026 (Thoughtworks). Use it as a starting point for evaluating the landscape, not as a verdict.

How do you use free CTO resources effectively?

Start with your gaps, not your interests. Take the CTO Readiness Assessment to find your weakest dimension, then pick one resource that targets it. Free resources have a hidden cost in your time and attention, so a short list used actively beats a long list skimmed.

• Read actively. For each book or article, write down the one or two ideas relevant to your situation, then apply them.
• Join one community and engage. Introduce yourself, ask questions and answer others'. The value comes from participation.
• Curate ruthlessly. Subscribe to two or three newsletters, not twenty.
• Apply the "would I pay for this?" test. If a free resource feels like marketing or is vague about specifics, drop it.

Go deeper

When you want structured assessment and targeted development, take the CTO Readiness Assessment, then use this guide to aim your learning at the gaps it finds. For structured programmes, see our review of engineering manager courses and CTO programs compared. For a complete map of CTO skills, read the CTO skills framework.

Frequently asked questions

What are the best free CTO resources?

For free reading, Will Larson's Irrational Exuberance blog, LeadDev's articles and reports, and StaffEng.com are the most useful. For research, the DORA programme at dora.dev is free. For peers, Rands Leadership Slack and the CTO Craft community are the best-known options. Pick one resource per skill gap rather than trying to cover everything.

What are the best communities for CTOs in 2026?

Rands Leadership Slack, CTO Craft, the Engineering Leadership Community and LeadDev's community are the best-known. Rands is open by emailed request, CTO Craft has a free community tier and is aimed at CTOs, and the Engineering Leadership Community runs application-based peer groups. Check each page for current membership terms before joining.

Where can a VP of Engineering find peer learning?

Peer groups and communities are the best fit: the Engineering Leadership Community runs application-based peer groups, CTO Craft runs mentoring circles facilitated by a CTO coach, and Rands Leadership Slack offers open conversation. For one-to-one support, a coach is a paid alternative. See our CTO coaching directory for options.

Which books should a new CTO read first?

Start with The Manager's Path by Camille Fournier if you are still moving from engineering into leadership, An Elegant Puzzle by Will Larson if you manage managers, and Accelerate if you need evidence for engineering investment. The Hard Thing About Hard Things suits startup CTOs facing decisions with no good option. All four are paid books.

Are there free resources for measuring engineering performance?

Yes. DORA publishes its software delivery metrics and research for free at dora.dev. The current model uses five metrics: change lead time, deployment frequency, failed deployment recovery time, change fail rate and deployment rework rate. The Accelerate book explains the research behind the original four key metrics.

Sources

1. DORA metrics: the four keys (current five-metric model) DORA, 2026
2. Generative organizational culture DORA, 2026
3. Documenting Architecture Decisions Michael Nygard (Cognitect), 2011
4. The Manager's Path (book description) O'Reilly Media, 2017
5. High Output Management Penguin Random House, 1995
6. An Elegant Puzzle Will Larson, 2019
7. Staff Engineer StaffEng.com, 2021
8. The Hard Thing About Hard Things Andreessen Horowitz, 2026
9. Accelerate IT Revolution, 2018
10. Team Topologies Team Topologies, 2025
11. Rands Leadership Slack Rands in Repose, 2025
12. CTO Craft CTO Craft, 2026
13. Engineering Leadership Community ELC, 2026
14. About LeadDev LeadDev, 2026
15. Technology Radar Thoughtworks, 2026