Book Review: Finding Direction in the Age of AI by Michael Earls

Finding Direction in the Age of AI opens not with a thesis but with a confession: Michael Earls didn’t set out to write a book at all. He started jotting down ideas so he wouldn’t forget them – notes after long workdays, thoughts that surfaced over early-morning coffee, fragments from conversations with colleagues. Over time those fragments began connecting around a single question that runs through every page: in a world moving at machine speed, how do we keep our direction?

That framing tells you exactly what kind of book this is. It is not a technical manual, and Earls says so plainly in the opening “How to Read This Book.” There are no frameworks to memorize and no diagrams to follow. Instead the book is a sequence of seven reflective chapters, each able to stand alone, that trace the arc of a twenty-plus-year technology career – from the physical world of cables, racks, and routing protocols, through the rise of cloud computing, to the present moment of artificial intelligence arriving as a daily companion in how we think and work. The chapters are bookended by a “Why This Book Matters Now” overview, a personal preface, an introduction, and a brief closing. It is a short book, and it reads quickly.

The central image is what Earls calls the digital compass – his answer to a world where the tools keep getting more powerful but clarity gets harder to find. Chapter 1, “Speed Without Direction Is Noise,” establishes the stakes through a rewatch of Hidden Figures, drawing the line between the era when a “computer” was a person solving equations by hand and the moment IBM’s machine arrived to change everything. The point lands: every generation faces its own wave of technological acceleration, and the tools change while the pattern does not. The chapter is anchored by two well-chosen personal moments – a visit to his daughter at the University of Cincinnati, where ambition and constant phone-driven distraction sit side by side, and an anecdote about losing GPS signal while driving Highway 1 and being forced to buy a paper map, which made him actually think about where he was going. “Sometimes we have to lose signal to find direction” is the kind of line that captures the book’s whole sensibility.

Chapter 2 makes the compass concrete, offering the closest thing to a framework the book contains: four practices – Recenter Often, Filter the Noise, Choose Your North, and Check Your Bearings – followed by a short “Goals and Next Steps” set (take a digital audit, establish quiet time, revisit your North). Earls leans on Simon Sinek’s “Start with Why” for the North-star idea and, more memorably, on the Ice Cube line “you better check yourself before you wreck yourself” as a reminder to pause before momentum carries you miles in the wrong direction. The advice is sound if not especially novel; its value is in the framing rather than the originality.

The book’s strongest material is in its two most personal chapters. Chapter 3, “When Direction Looked Like a Destination,” is the standout – a genuinely thoughtful piece on leadership built around the admission that “you can climb fast and still be going the wrong way.” Earls describes once stepping backward in his career on paper to reach where he was trying to go, and the slow realization that his real strength was never just performance but building people. The passage on the leaders who shaped him – the ones who started with who he was rather than with “let’s review that MBR,” who saw his strengths before his gaps – is the emotional core of the book, and his definition of leadership (“helping people grow into who they already are – just more fully”) is the line most likely to stay with readers.

Chapter 4, “Cloud Was Never About Servers,” is the most vivid and specific, and it benefits enormously from Earls’s actual hands-on history. The recollections are concrete in a way the rest of the book sometimes isn’t: the leap from half-duplex to full-duplex networking, the arrival of 10-gig, pizza-box servers stacked in racks, blade chassis, BGP and dark fiber linking datacenters, /24 prefixes engineered to vanish from the network under isolation conditions. Best of all is the buried gem about building an open-source centralized logging tool, php-syslog-ng, years before platforms like Splunk made that idea a category – built simply to solve a real problem and handed to the community, with no thought of startups or venture capital. From this lived foundation Earls makes his cleanest argument: cloud was never about renting servers but about removing the constraints servers imposed, abstracting infrastructure so that builders could focus on possibilities, with identity emerging as the new control plane. The chapter earns its conclusions because the author has clearly done the work.

Chapter 5, “The Day the Water Cooler Disappeared,” turns to what gets lost as work goes fully digital. Earls – who by his own Delta tally was traveling roughly 85% of the time before 2020 and nearly hit million-miler status – uses the COVID rupture to mourn the unscripted moments where culture actually forms: the phone-free morning coffee ritual with a teammate, the hallway debate, the end-of-day “let’s grab a drink.” His observation that “culture happens in the gaps” is well put, and the personal note that he met his wife because two people shared the same physical space gives the argument weight. Chapter 6, “AI, Agents, and the Future of Work,” is the most forward-looking, reframing AI adoption as something that begins not with world domination but with “removing clicks,” positioning AI as the trusted colleague down the hall and exploring a future where people orchestrate teams of agents rather than execute every task themselves. The chapter’s recurring instinct – that the right question is “what problem are we actually trying to solve?” rather than “will this replace people?” – is its most useful contribution. Chapter 7 and the brief closing return to the book’s emotional register, with a sailing metaphor about finding rhythm and a final, deliberately small invitation: “Happy hour starts in five. Let’s go.”

Where the book is honest, it is also limited. Its brevity is a double edge – the reflective, one-chapter-at-a-time structure keeps it readable, but it also means several ideas are stated rather than developed, and the AI chapter in particular stays optimistic and surface-level, sidestepping the harder questions about labor, accountability, and risk that its own subject raises. The bigger issue is repetition: the core refrain – speed without direction is noise; innovation moves at machine speed while leadership moves at human speed – appears in the overview, the preface, the introduction, and the closing of nearly every chapter. By the final pages it has been earned several times over and then restated several more. The pop-culture scaffolding (Hidden Figures, Field of Dreams, Spaceballs, The Matrix, I, Robot, Superman) is charming and accessible but leans on familiar touchstones to carry ideas that occasionally needed the author’s own sharper articulation instead. Readers looking for a rigorous, argued treatise on AI and leadership will find this lighter than expected. Readers who take it for what it announces itself to be – a sincere, experienced practitioner’s set of reflections, closer to a long conversation than a guidebook – will find it warm, grounded, and genuinely worth the short time it asks.

Rating: ★★★★½

Verdict: Finding Direction in the Age of AI by Michael Earls is a warm, sincere, and refreshingly humble set of reflections from someone who built the infrastructure he writes about and lived through every shift he describes. It is light and at times repetitive, and it doesn’t pretend to be a definitive guide – but its leadership chapter and its from-the-trenches account of the cloud era give it real substance, and its central reminder is one worth keeping close: speed is everywhere, but direction is still something we choose.