In this book, Patrick Kua gathered a lot of interviews from multiple people that are or were, at some point, playing the role of Tech Lead in a team.
He starts off by defining what he is calling Tech Lead and how hard it is to tackle the role as most people are not really trained or prepared for it. His definition of Technical Leader is:
“A leader, responsible for a development team, who spends at least 30 per cent of their time writing code with the team."

The book evolves into a series of interviews grouped in terms of 2 major parts, novice and practitioners.

In the Novice part, Patrick goes into a bit of describing what he sees in common in Tech Leads that are novices in the matter.
  1. Looking to the future, not as much the present, of the project/code
  2. Sensing greater responsibility
  3. Guiding the Technical Vision
  4. Less time for writing code
  5. Juggling more context switches
  6. Allowing people to fail
  7. People aspects are hard. Maybe the hardest.

The book moves on to display a series of interviews that Patrick conducted with many people. The interview is fairly consistent and asks people to answer:
  1. Describe what responsibilities the Tech Lead has and/or Does the role of Tech Lead hold any surprises?
  2. The pros and cons
  3. Any preparation advice?
  4. Where do you go for support?
  5. Has your perspective changed?
  6. The interviewee’s key question and their answer
  7. The interviewee’s background

At about 25% of the book, Patrick moves to the Practitioners section. He describes a little bit what he sees in common for practitioner Tech leads:
  1. People
    1. Remaining technically grounded
    2. Finding and developing good people
    3. Listening to the team
    4. Appreciating individual strengths
  2. The Tech of a Tech Lead
    1. Guiding the technical solution
    2. Harmonising team direction
    3. Managing technical risks
    4. Taking a longer-term view
  3. Bridging the Business with Tech
    1. Building trust
    2. Finding time for technology
    3. Making technology solutions easy to understand
    4. Influencing planning
    5. Championing business needs
  4. You
    1. Adapting to new circumstances
    2. Making yourself redundant
    3. Using your own strengths

And follows a similar interview style approach for the rest:
  1. What should a Tech Lead focus on and why?
  2. What has been your biggest challenge as a Tech Lead?
  3. Any time-management tips?
  4. How do you strike the right balance between writing code and dealing with other issues?
  5. The interviewee’s question and their answer
  6. The interviewee’s background

Pat finishes the book drawing some conclusions from the interviews and summarizing the learnings.

The book can get a little tiring due to the interview format being a little repetitive but the content is very reassuring for new tech leads and provides a few insights for those who have been doing the work for a while. In short, I recommend the book if you are thinking about what being a tech lead is, hope to become a tech lead or are a tech lead. If you can pace yourself to read one or two interviews a day, you’d probably spend 5 to 10 minutes a day with the book and be done within the month. Probably better that way than trying to read the whole book in a single shot.