# Big-O Without the Math Panic

If your eyes have ever glazed over at a wall of `O(n²)` and `Θ(log n)` on a whiteboard, take a breath.
You don't need any of that to understand what Big-O is *for*. Underneath the scary notation is one
plain, useful question: **when my data gets bigger, does the work get a little bigger, a lot bigger, or
disastrously bigger?** That's it. That's the whole idea, and you already think this way in real life.

This guide gives you the mental model first - no proofs, no summation symbols, no "left as an exercise
for the reader." By the end you'll be able to glance at a piece of code and say, with calm confidence,
"this one's going to fall over when the data grows" - which is the thing Big-O was actually invented to
help you do.

## How to read this
- **Want it to finally make sense?** Read in order - each phase builds on the last, and they're short.
- **Just need to name a Big-O from some code in front of you?** Skip to the
  ["name it from the code" table](02-the-few-you-actually-meet.md) in Phase 2.

## The phases
1. **[It's About How Things GROW](01-its-about-how-things-grow.md)** - Big-O isn't about exact speed;
   it's about how the *work* grows as the *input* grows. The one question to keep asking.
2. **[The Few You Actually Meet](02-the-few-you-actually-meet.md)** - the small handful you'll see in
   real life - constant, linear, quadratic, logarithmic, and `n log n` - in plain language, with a
   table for naming them straight from the code.
3. **[Why It Matters in Real Life](03-why-it-matters-in-real-life.md)** - the same code that's fine at
   100 items and dies at 10 million, the accidental-quadratic trap, and how picking the right data
   structure quietly changes your Big-O.

> This guide is the intuition. The formal definitions - limits, the difference between Big-O, Big-Θ
> and Big-Ω, and how to *prove* a bound - are a separate, more advanced topic. You don't need them to
> reason well about everyday code, and they're deliberately left out here.

Related: [Data Structures, Explained](/guides/data-structures-explained) ·
[What "Performance" Actually Means](/guides/what-performance-means)