As many of us do, I have a much longer “To be Read” list than I have hours in the day to read. That said, I have a set of books I really plan to get through this summer, and I thought I would share (hey, it works for Bill Gates!). People who know me know I read, a lot. However I always fall into the trap of reading nothing but technology and business books. So in this list, I am trying force myself to include some broader material into my summer. The list is in no particular order, though.
One Drum by Richard Wagamese
This is one of those “not directly work related” books on my list (and really is first in my queue). Richard Wagamese (1955–2017) was an accomplished Canadian author and journalist of Ojibwe descent. He is best known for his works of fiction, non-fiction, and poetry that explore themes of indigenous identity, trauma, and healing. Wagamese’s writing was deeply influenced by his personal experiences, including his struggles with homelessness and addiction.
In One Drum, Wagamese delves into a rich tapestry of Ojibway wisdom, known as the Grandfather Teachings. The book guides readers through essential life lessons—humility, respect, and courage. Beyond mere lessons, it also outlines accessible ceremonies, designed for anyone, in any location, solo or in a group setting. These ceremonies serve as practical tools to cultivate unity and interconnectedness.
Stranger in a Strange Land by Robert Heinlein
Purely a fun read. I have read Stranger in a Strange Land many times, but it has probably been 20 years. This has always been my favourite Heinlein novel, as it is full of provocative (especially for when it was written) ideas on religion, politics and sexuality.
I recall the first time I read it, I was in grade 9 and had chosen it for a book report for school. When I showed it to my English teacher, he looked very concerned and asked, “Do you parents know you are readying this?” Of course they did – my mother recommended it!
The CheckList Manifesto by Atul Gawande
Ok, back to work! The CheckList Manifesto is an exploration of the role checklists can play in our professional and daily lives. The book asserts that checklists serve as a shield against failures, raising the bar for baseline performance. However, it also emphasizes that checklists are merely aids, and their efficacy is dependent on their utility; if a checklist does not help in accomplishing a task, it’s not fit for purpose.
I am looking at it from the perspective of “how can this help me tune processes in development and support?” Never know where you might find useful tools.
Build by Tony Fadell
Build by Tony Fadell is essentially about “how to build a transformative product-based business”. Fadell, known for his pivotal role in the creation of the iPhone and the founding of Nest, a smart home device company later sold to Google for billions, shares his unique journey and invaluable insights. The book charts Fadell’s career trajectory, including his early failures in smartphone development before the groundbreaking success of the iPhone, but it also promises advice for success at all career stages and tips for building successful product-based businesses and teams. The book provides a comparative analysis of Fadell’s guidance with the advice of other experts in the field, presenting a comprehensive resource for those aiming to create successful products, businesses, and teams.
I am of two minds on this one, as I find these books are often way too anecdotal and seem to degenerate into “war stories” and “how cool were we” stories. Trying to keep an open mind though!
The Language Instinct: How the Mind Creates Language by Steven Pinker
The Language Instinct: How the Mind Creates Language by renowned Harvard psychologist and linguist Steven Pinker, argues that human beings acquire language primarily through an instinctual process. This instinct, which is guided by human instruction, naturally evolves as infants grow within their communities. Pinker’s work explores the fascinating intersection of linguistics, psychology, and child development, asserting that our capacity for language is not solely a learned skill but a fundamental human instinct.
This is another just-for-fun entry in the list. I have always been fascinated by language, how it developed, and specifically how it relates to our thought processes (is language necessary for cognitive thought? did intelligence come before language or did they co-evolve? Does the language we we think in constrain what/how we think?). This book is from 1994 but should still be interesting.
The Order of Time by Carlo Rovelli
More just-for-fun reading! The Order of Time by Carlo Rovelli is an exploration into the concept of time. In this work of philosophical science, Rovelli contends that time is not a constant or universally accepted entity as dictated by natural or scientific laws. Instead, he proposes that time is an illusion, sculpted by our individual realities and experiences. This innovative perspective invites readers to reconsider their understanding and perception of time.
Just something to keep my brain busy on a Saturday night!
Clean Architecture: A Craftsman’s Guide to Software Structure and Design by Robert C. Martin
Ok, pure work book here. I read a lot about “architecture” but tend towards discussions of specific architectures, practical considerations, pros and cons, etc. It has been a while since a I read about architecture in a broader, more general sense. I may actually have read all or part of this before, but anything by Robert C. Martin is typically worth revisiting.
Clean Architecture: A Craftsman’s Guide to Software Structure and Design by Robert C. Martin, also known as Uncle Bob, presents a set of universal rules of software architecture aimed at improving developer productivity across the lifespan of a software system. The book builds on Martin’s previous works, offering not just options, but crucial choices for software success. It is filled with direct solutions to real challenges that could make or break projects. Readers learn what software architects need to achieve, essential software design principles for addressing function, component separation, and data management, and understand programming paradigms that impose discipline by restricting what developers can do. The book also provides guidance on the implementation of optimal, high-level structures for various applications and outlines how to define appropriate boundaries, layers, organize components and services. It discusses common pitfalls in designs and architectures and provides solutions to prevent or correct these failures. This book is considered a must-read for every current or aspiring software architect, systems analyst, system designer, software manager, and programmer.
Staff Engineer: Leadership beyond the management track by Will Larson
I came across this book last winter when I was thinking through a number of work-related challenges (replacing my Director of Development who had just moved on to a new opportunity, hiring/developing more senior resources for the dev team, and better defining what a career path in software/technology looks like especially for those not interested in management). I have read parts of this book already, but really want to read it cover-to-cover.
Staff Engineer: Leadership beyond the management track by Will Larson is described as a valuable guide that elucidates the role of a Staff Engineer. Compiled from numerous interviews with established Staff+ engineers, the book offers diverse insights into the paths to becoming a Staff engineer and strategies to flourish at this level. Key ideas include self-scaling and growth, influencing others, and problem-solving. The book emphasizes the importance of writing for clarity and scaling oneself, investing time in high-value work, and balancing this with personal growth. It also underscores the necessity of being present in strategic meetings and taking the initiative to tackle and define problems.
So there is my list for the summer (assuming I do not get distracted by something shiny!). So what’s on your list?
Monday Morning CTO 