Prerequisites and Background

What You Need to Know Before Starting

Essentially nothing. This textbook assumes no prior knowledge of statistics, psychology, sociology, network theory, or philosophy. Everything is introduced from first principles.

More specifically:

Mathematics

You need basic arithmetic and the concept of fractions. That's it. When we discuss probability, we'll build from "out of 100 people" intuitions before introducing any notation. When we discuss expected value, we'll use plain multiplication before mentioning the word "formula."

Part 2 is the most mathematically intensive section of the book. Even there, the goal is intuition — genuine understanding of what mathematical concepts mean — not computational proficiency. If you can calculate 50% of a number, you have the math background required.

Optional enhancement: If you've taken a statistics course or AP Stats, you'll find Part 2 more familiar. You might skim the definitional sections and focus on the "why it matters for luck" applications.

Psychology

No prior coursework required. We introduce all psychological concepts as they appear. Familiarity with terms like "cognitive bias" or "confirmation bias" is helpful but not assumed.

Sociology

No prior coursework required. Network theory (Part 4) is introduced from scratch — including what a network is, what nodes and edges mean, and why structure matters. If you've taken intro sociology, you'll recognize some concepts; the application to luck is new regardless.

Philosophy

Part of Chapter 39 engages with the philosophical debate about moral luck. No prior philosophy background is required; the relevant positions are explained as needed.

Technology / Social Media

The book uses social media platforms (TikTok, Instagram, YouTube, LinkedIn) as running examples throughout. Familiarity with these platforms as a user is helpful. Understanding of how algorithms work is not assumed — we develop that understanding through the text.

Python (for code chapters)

Code chapters include Python simulations. To run the code, you'll need Python 3.10+ installed and the ability to install packages with pip. To understand the code conceptually, no programming experience is required — every script is heavily commented. If you have zero programming background, read the code as commented prose; the logic will be clear even if the syntax isn't.

Recommended Background Reading

Not required, but these books will deepen your engagement with the material:

For probability intuition: - How Not to Be Wrong by Jordan Ellenberg — accessible, brilliant mathematics with real-world application

For the psychology of luck: - The Luck Factor by Richard Wiseman — the foundational popular book on luck science; some of the research discussed in Chapter 12

For network theory: - The Tipping Point by Malcolm Gladwell — engaging introduction to network dynamics (note: some claims have since been complicated by replication) - Connected by Nicholas Christakis and James Fowler — deeper, more rigorous treatment

For the luck-skill debate: - The Success Equation by Michael Mauboussin — the most systematic treatment of luck vs. skill across domains

For serendipity: - The Serendipity Mindset by Christian Busch — the current leading scientific treatment

A Note on Reading Speed and Style

This is a dense book. Not difficult — but dense. The goal is substantive coverage, which means some chapters reward slower reading than others.

Suggested reading pace: - Main chapter text: 45–90 minutes per chapter, with pauses for reflection - Exercises: Budget 30–90 minutes depending on depth - Case studies: 20–45 minutes each, ideally discussed with others

If you're using this in a course, a pace of two to three chapters per week is sustainable for a semester-long course. Reading it independently, most readers find a chapter every two to three days a comfortable rhythm that allows for genuine absorption.

The most important thing: don't just read. Engage. Answer the embedded questions in your head or on paper. Try the Python simulations. Discuss the case studies. The concepts here are not just intellectually interesting — they're practically useful, and they only become useful when they move from the page to your thinking.