Front Matter
How to Read This Book
Free to read · 7 min read · begins on page 22
The book is long. About four hundred and fifty pages by the time you reach the back cover. You are not required to read all of them in order, and depending on who you are, you probably should not.
This short section walks you through how the chapters are built and which order to read them in. Five minutes here will save you hours later. How a chapter is built Every career chapter follows the same structure. By the third or fourth chapter you will recognize the rhythm without thinking about it. Knowing the structure now lets you skim sections that do not apply to you and sit with the ones that do.
Each chapter has eight sections.
The opening framing. A few pages that introduce the role from a particular angle. Usually a metaphor, a historical comparison, or an observation about the role that the rest of the chapter then unpacks. If you are short on time and just want to know what argument the chapter makes, the opening framing tells you in five minutes.
The history. What the role used to be, where it came from, what value it produced. Most chapters include a historical analog, a previous profession that was compressed by a previous tool. The lawyer being compressed by AI has scribes being compressed by the printing press. The graphic designer has the calligrapher. The actuary has the human computer. These analogs are not throwaway color. They are the reason to take the current compression seriously, because the previous ones happened too.
The compression. What AI is doing inside the role right now. Named tools, specific examples, before-and-after comparisons. This is the longest section in most chapters because it is where the evidence lives. In some chapters this section anchors a passage from my own direct experience: something I have done, witnessed up close, or had to make a decision about. Those passages are evidence, not memoir.
What cannot be compressed. The residual high-value work that AI does not yet touch. Judgment, taste, political navigation, accountability, the willingness to refuse. This section is where the book does its most important work, because it is where the reader figures out which side of the compression they live on.
The playbook. Specific, sequenced principles for the practitioner. Written in second person. You should do this. You should adopt this stack. You should move up this ladder. The playbook gives the reader frameworks they can adapt.
What I Would Do. A first-person section where I tell you, plainly, what move I would make if I were in the role tomorrow. A week-by-week walkthrough that ends with one sharp single-move recommendation. This section is the book's signature move. It is calibrated to my actual proximity to the career: confident and detailed where I have direct experience, more careful where I do not. The single-move close at the end of every chapter is the line worth remembering.
The uncomfortable truth. What is being lost, named honestly. The book is not interested in pretending the transition is painless. This section is short, sometimes the shortest in the chapter, but it is the emotional spine of the book.
What this opens up. The forward-leaning close. What new businesses, new roles, new opportunities become available given the compression of this specific career. Each chapter ends here so the reader closes the chapter feeling oriented toward action, not loss.
If you read every section of every chapter, you will have read about a hundred and seventy thousand words. If you read the framing, the compression, and What I Would Do across all twenty-five chapters, you will have read about half that and gotten most of the value. Both are legitimate ways to use the book. How to read the book based on who you are The book is designed for several different readers. The right reading order depends on which one you are.
If you are early in your career, somewhere between your first job and your fifth year of work, here is the order. Read the preface and the introduction. Read the chapter for your current career. Read three or four other chapters that interest you, sampled across different parts of the book, to see the shape of the broader pattern. Read chapter 27, "The People Who Win and the People Who Lose." Read chapter 30, the closing letter.
What you can skip on the first pass: the chapters in parts of the book that do not touch your current trajectory, and the historical sections in chapters where the history is more for context than for action. You can come back to them later if the book holds up for you.
If you are mid-career, somewhere between your fifth year and your fifteenth, here is the order. Read the preface and the introduction. Read the chapter for your career, then read the chapters for the careers immediately adjacent to yours. If you are a product manager, read product manager, project manager, and consultant. If you are a copywriter, read copywriter, content writer, and marketing manager. The adjacencies are where you will find the moves you have not yet considered.
After that, read chapter 27 (who wins and loses), chapter 28 (what becomes buildable), and chapter 30 (the letter). Mid-career is the audience the book was most directly built for, and the closing chapters are written with you in mind.
If you are senior, in a leadership role or close to one, here is the order. Read the preface and the introduction. Read the chapters in the parts that affect your team. If you run a product organization, read all of part four. If you run a marketing organization, read part two and the marketing chapters in part four. Skim the parts that do not directly affect your team, but at least read the framing sections, because some of the patterns you need to see are visible only when you look across multiple parts.
After that, read the entire closing section. Chapter 26 (the compression pattern), chapter 27 (who wins and loses), chapter 28 (what becomes buildable), chapter 29 (what cannot be compressed), and chapter 30 (the letter). The closing section is written with senior readers in mind because the questions it asks are the questions you are going to have to answer in the next two to three years inside your own organization. If you are a founder or builder, or if you are quietly considering becoming one, here is the order. Read the preface and the introduction. Read chapter 28, "What Becomes Buildable," before you read anything else, even though it is near the end of the book. Then read the chapter for your current career and the chapters for the careers your potential business would serve or replace. Then read whatever else holds your attention.
The book is partially written for you. The compression of expertise into tools is not just a threat to careers. It is also the largest opportunity to build a small, profitable, AI-augmented company that any of us has seen in our lifetimes. Chapter 28 lays out the specific shapes that opportunity is taking. The career chapters give you the raw material for thinking about which compression you want to ride.
If you are reading the book to understand what is happening to work, without a specific career angle, read it cover to cover. The book is built for that reader too. The architecture rewards patience. The threads accumulate. The closing section earns its weight only after the twenty-five chapters before it. A few things worth knowing before you start The book is honest. Sometimes uncomfortably so. There are passages where I tell readers, plainly, that the careers they have invested in are being hollowed out and that they should think hard about whether to stay. There are passages where I describe decisions I have personally made about people I have hired, decisions that went the wrong way for those people. The book does not soften these passages, because softening them would be dishonest, and the book is built on the premise that the reader is better served by the truth.
The book is also specific. Where I name tools, I name specific tools. Where I name companies, I name specific companies. Where I make claims about how fast something is happening, I tie the claim to specific time markers. This is not because the specifics will all hold up two years from now. The tools will change. Some of the companies will go out of business. The pace claims may turn out to be wrong in either direction. The specificity is there because the alternative is the kind of vague AI writing that is everywhere and that is useful nowhere.
The book repeats itself, in a structured way. The eight themes named in the introduction surface in different forms across the twenty-five chapters. By the time you finish the book, you will have seen each theme play out in many contexts.
This is intentional. The book is making a cumulative argument, and the argument lands by accumulation rather than by force. If you find yourself thinking "I have seen this pattern before, in a different chapter," that is the book working as designed.
The chapters are not equal in tone. Some are sharper. Some are gentler. Some are more analytical. Some are more emotional. The voice is the same throughout, but the texture adjusts to the career. The chapter on photographers is going to feel different from the chapter on actuaries, and both are going to feel different from the chapter on lawyers, because the people in those careers respond to different registers and the book respects that.
That is the book. The next thing you read is the first part-opener, which frames the Code and Numbers People before chapter one introduces the career we are starting with. The software engineer is the canary, and the canary is where we begin.