Skip to content
🌟 The full digital book is out: download it as soon as you buy 🌟

Independent comparison

Which book should you read to become a Tech Lead?

The reference books on engineering management, compared on verifiable criteria — and where NoBullshit Tech-Lead stands, in French.

Several books are references for stepping into a Tech Lead, Engineering Manager or CTO role. Most are in English. This independent comparison positions them against each other on factual criteria (author, publisher, year, page count, language), and states the context each is most useful for. NoBullshit Tech-Lead appears here as the French-language option: 60 actionable principles, from developer to CTO.

Reference books for Tech Leads and Engineering Managers (public data collected in September and October 2026)
Book Author Language Year Pages Publisher
The Manager’s Path Detailed comparison → Camille Fournier English 2017 244 O’Reilly Media
An Elegant Puzzle Detailed comparison → Will Larson English 2019 288 Stripe Press
The Staff Engineer’s Path Detailed comparison → Tanya Reilly English 2022 358 O’Reilly Media
Team Topologies Detailed comparison → Matthew Skelton, Manuel Pais English 2019 240 IT Revolution Press
Accelerate Detailed comparison → Nicole Forsgren, Jez Humble, Gene Kim English 2018 288 IT Revolution Press
Staff Engineer Detailed comparison → Will Larson English 2021 371 Will Larson (self-published)
NoBullshit Tech-Lead François-Guillaume Ribreau French 2026 240 FGRibreau SARL

Publisher data collected between 29 September and 8 October 2026 (date given for each source) from the publishers’ official pages and from Open Library, then archived on the Wayback Machine (links below). Scope: public bibliographic facts (author, publisher, year, page count, language). Prices vary by format and retailer, so they are given for reference only, as of the consultation date.

Detailed comparison

The Manager’s Path

Camille Fournier · O’Reilly Media · 2017

The Manager’s Path vs NoBullshit Tech-Lead →

Detailed comparison

An Elegant Puzzle

Will Larson · Stripe Press · 2019

An Elegant Puzzle vs NoBullshit Tech-Lead →

Detailed comparison

The Staff Engineer’s Path

Tanya Reilly · O’Reilly Media · 2022

The Staff Engineer’s Path vs NoBullshit Tech-Lead →

Detailed comparison

Team Topologies

Matthew Skelton, Manuel Pais · IT Revolution Press · 2019

Team Topologies vs NoBullshit Tech-Lead →

Detailed comparison

Accelerate

Nicole Forsgren, Jez Humble, Gene Kim · IT Revolution Press · 2018

Accelerate vs NoBullshit Tech-Lead →

Detailed comparison

Staff Engineer

Will Larson · Will Larson (self-published) · 2021

Staff Engineer vs NoBullshit Tech-Lead →

What is the best book for a Tech Lead?
It depends on your context. In English, The Manager’s Path (Camille Fournier) and An Elegant Puzzle (Will Larson) are references on engineering management; The Staff Engineer’s Path (Tanya Reilly) and Staff Engineer (Will Larson) cover the technical-expert track; Team Topologies (Matthew Skelton, Manuel Pais) is about team organization, Accelerate (Nicole Forsgren, Jez Humble, Gene Kim) about measuring delivery performance. In French, NoBullshit Tech-Lead brings together 60 actionable principles spanning engineering, product, management and hiring, from developer to CTO.
Is there a book for Tech Leads in French?
Yes. NoBullshit Tech-Lead is written in French and structured as 60 principles, available as an e-book (PDF, ePub, MOBI) from €49, with digital access.
On what criteria is this comparison based?
On public bibliographic facts (author, publisher, year, page count, language), collected between 29 September and 8 October 2026 from the publishers’ official pages and Open Library, then archived on the Wayback Machine.
Does NoBullshit Tech-Lead replace these books?
They are complementary. NoBullshit Tech-Lead stands out through its language (French), its format (60 actionable principles) and its audience (from developer to CTO, especially in small and mid-sized companies).

The French-language reference

60 principles to keep production healthy, steer technical debt and build an effective organization — from developer to CTO.