#0122 - How to be a good technical leader with Sander Hoogendoorn

This book provides a detailed approach to implementing Continuous Delivery, focusing on automation and collaboration between development, testing, and operations teams. It emphasizes the importance of keeping software in a releasable state and highlights the benefits of frequent, low-risk deployments.

In this book, Frederick P. Brooks discusses several key issues in software engineering, most notably 'Brooks's Law,' which states that adding manpower to a late software project makes it later. The book explores the complexities of large programming projects, the difficulties in measuring work in 'man-months,' and the importance of effective communication and team management. It also includes insights from Brooks's experience managing the development of IBM's System/360 and OS/360.

In this book, Mark Manson argues against the typical self-help advice of constant positivity, instead suggesting that life's struggles give it meaning. He emphasizes the need to focus on what truly matters and to accept and confront painful truths. The book is divided into nine chapters and uses blunt honesty and profanity to illustrate its ideas, encouraging readers to find meaning through values they can control and to replace uncontrollable values with more meaningful ones.

The Pragmatic Programmer is a book that centers on how to use software to solve problems effectively and how to grow as a developer pragmatically. It was first published in 1999 and a 20th Anniversary Edition was released in 2019. The book emphasizes key qualities such as being an early adopter, having fast adaptation, inquisitiveness, critical thinking, realism, and being a jack-of-all-trades. It uses analogies and short stories to present development methodologies and caveats, including concepts like DRY (Don't Repeat Yourself), YAGNI (You Aren't Gonna Need It), and rubber duck debugging. The book covers topics such as writing clean code, estimating software delivery, instituting change, combating stagnancy, and making software processes resilient and efficient through automation and testing.