Reality Has a Surprising Amount of Detail (2017)
Meta Description: Discover why "Reality has a surprising amount of detail" (2017) remains one of the most impactful essays on observation, learning, and expertise. Practical lessons inside.
TL;DR: John Salvatier's 2017 essay "Reality Has a Surprising Amount of Detail" argues that the world is far more complex than it appears until you actually try to do something. This insight has profound implications for how we learn, build products, communicate, and approach expertise. This article breaks down the core ideas, why they matter in 2026, and how you can apply them immediately.
What Is "Reality Has a Surprising Amount of Detail"?
In 2017, programmer and researcher John Salvatier published a short but remarkably dense essay on his blog. The central thesis was deceptively simple: the real world contains an almost incomprehensible amount of detail that you cannot perceive until you engage with it directly.
Salvatier illustrated this with a mundane example — building a set of stairs. Before you start, stairs seem simple. Wood, nails, a slope. But once you actually begin, you encounter a cascade of sub-problems: the wood warps, the floor isn't level, the nails split the grain, the angle feels wrong underfoot. Each solution reveals three more problems you hadn't anticipated.
This essay, often referred to as "Reality has a surprising amount of detail (2017)," became quietly influential in tech, product design, philosophy, and education circles. Nearly a decade later, it remains one of the most-shared pieces of writing among engineers, founders, and anyone who has ever tried to build something real.
[INTERNAL_LINK: epistemic humility in product development]
The Core Argument: Why We Underestimate Complexity
The Illusion of Simplicity
Salvatier's key observation is that things look simple from the outside precisely because we lack the vocabulary to see their complexity. When you don't know anything about carpentry, you can't see the grain direction in wood. When you don't know anything about cooking, you can't see why a sauce is breaking. The details are invisible until you develop the perceptual apparatus to notice them.
This is not a minor cognitive quirk. It has massive consequences:
- We chronically underestimate how long things take
- We dismiss experts as "gatekeepers" when they're actually navigating invisible complexity
- We assume our first plan will work
- We get frustrated when reality doesn't cooperate
The Staircase Metaphor in Practice
The staircase example is so effective because stairs genuinely do seem trivial. And yet professional carpenters spend years learning their craft. Why? Because reality has a surprising amount of detail — the phrase is almost a mantra once you internalize it.
Consider these real-world parallels:
| Domain | What It Looks Like | What It Actually Involves |
|---|---|---|
| Software development | "Just build an app" | State management, edge cases, security, scaling |
| Cooking | "Just follow the recipe" | Heat control, timing, ingredient quality, technique |
| Writing | "Just put words down" | Structure, voice, audience, revision, clarity |
| Parenting | "Just love your kids" | Sleep schedules, developmental stages, emotional regulation |
| Starting a business | "Just sell something people want" | Legal, logistics, marketing, hiring, cash flow |
Every domain, once entered, reveals layers that were invisible from outside.
Why This Essay Became So Influential
It Named Something People Had Felt But Couldn't Articulate
One reason "Reality has a surprising amount of detail (2017)" spread so widely is that it gave language to a near-universal experience. Almost everyone has started a project — renovating a bathroom, writing a novel, launching a side hustle — and been blindsided by how hard it was.
Before Salvatier's essay, people often blamed themselves ("I must be bad at this") or blamed the domain ("This field is unnecessarily complicated"). The essay reframes the experience: complexity is the default state of reality, not an anomaly.
It Has Practical Implications for Expertise
The essay also reframes what expertise actually is. An expert isn't someone who has memorized facts — they're someone who has developed perceptual sensitivity to the relevant details in a domain.
This is why:
- A senior engineer can look at a codebase and immediately sense architectural problems
- An experienced investor can read a pitch deck and spot the fatal flaw in 30 seconds
- A master chef can taste a dish and know exactly what's missing
They're not magic. They've simply accumulated the ability to see what's there.
[INTERNAL_LINK: how expertise develops over time]
Applying the Insight: Practical Lessons for 2026
Lesson 1: Approach New Domains With Radical Humility
The first and most important lesson from "Reality has a surprising amount of detail (2017)" is to assume you are missing most of the relevant detail when entering any new domain.
This doesn't mean paralysis. It means:
- Talk to practitioners early — not to get their opinion, but to discover what questions you don't even know to ask
- Start small and iterate — your first version will be wrong in ways you can't predict
- Budget for the unknown — in time, money, and emotional energy
A useful tool for capturing what you don't know is structured journaling. Roam Research is excellent for building a personal knowledge graph that helps you track evolving understanding as you learn. It's not cheap at $15/month, but for serious learners and researchers, the networked note-taking format mirrors how expertise actually develops.
Lesson 2: Re-Evaluate Your Frustration With Experts
One of the most immediately useful applications of this insight is changing how you relate to people who seem to be gatekeeping or overcomplicating things.
When a contractor tells you a renovation will take three months and you think it should take three weeks, the most likely explanation is not that they're padding their estimate — it's that they can see the details you can't.
This doesn't mean experts are always right. But it does mean the burden of proof is on the person with less domain experience, not the other way around.
Lesson 3: Use This to Become a Better Communicator
If you're the expert in a room, "Reality has a surprising amount of detail (2017)" is a reminder that your audience cannot see what you see. This is the root cause of most technical communication failures.
Practical techniques:
- Start with the problem, not the solution — help people build the context that makes your answer legible
- Use concrete examples before abstract principles — let people feel the complexity before naming it
- Invite questions that reveal what they can't see yet — "What seems weird or counterintuitive about this?" is a powerful prompt
For teams doing technical communication, Loom is a genuinely useful tool for recording walkthroughs where you can show complexity visually. The free tier is generous and the async video format lets viewers pause and rewatch the details they'd miss in a live presentation.
Lesson 4: Build Better Products and Systems
For product designers and engineers, this essay is a design principle in disguise.
Users cannot see what you see. They will interact with your product with a mental model that is missing almost all the detail you take for granted. This means:
- Error messages need to be far more explicit than you think
- Onboarding needs to surface complexity gradually, not all at once
- "Obvious" features are only obvious to people who already understand the system
[INTERNAL_LINK: user onboarding best practices]
The field of UX research exists largely to solve this problem — to help teams discover the details users encounter that designers couldn't predict. Tools like Maze allow you to run rapid usability tests with real users and surface the unexpected friction points. Honest assessment: Maze is powerful but has a learning curve itself, and pricing scales quickly for larger teams.
Lesson 5: Reconsider How You Plan Projects
Project planning is one of the areas most devastated by the underestimation of detail. The planning fallacy — our tendency to underestimate time and costs — is well-documented in behavioral psychology. Salvatier's essay provides the mechanism: we plan based on the details we can see, which are always a fraction of the details that exist.
Practical countermeasures:
- Reference class forecasting: look at how long similar projects actually took, not how long they seemed like they should take
- Pre-mortems: imagine the project failed and work backward to identify what you missed
- Buffer multiplicatively, not additively: if you think it'll take 2 weeks, plan for 4-6, not 2.5
For project management, Linear is one of the better tools for software teams that want to track complexity honestly. Its issue tracking is fast and the cycle time analytics help you build a realistic picture of how long things actually take in your specific context. It's genuinely excellent, though it's primarily built for engineering teams.
The Philosophical Dimension: What This Means for Knowledge
Tacit Knowledge and the Limits of Description
Salvatier's essay connects to a rich tradition in philosophy of knowledge, particularly the concept of tacit knowledge developed by Michael Polanyi. Polanyi famously wrote that "we can know more than we can tell" — meaning that much of what experts know is embedded in perception and action, not in explicit rules.
This is why:
- Reading a book about swimming doesn't teach you to swim
- Studying management theory doesn't make you a good manager
- Knowing the rules of chess doesn't make you a strong player
The details live in the doing.
Epistemically, This Should Make Us More Humble About Strong Opinions
If reality has a surprising amount of detail in every domain, then strong opinions formed without direct engagement are almost certainly missing crucial information. This is not an argument for relativism — some things really are better than others. It's an argument for calibrated confidence: being more certain about things you've engaged with directly and more uncertain about things you've only observed from outside.
[INTERNAL_LINK: epistemic calibration and decision making]
Key Takeaways
- "Reality has a surprising amount of detail (2017)" by John Salvatier argues that the world is far more complex than it appears until you directly engage with it
- Complexity is the default, not an anomaly — this reframes frustration as information rather than failure
- Expertise is perceptual: experts have developed sensitivity to details that are invisible to novices
- Approach new domains with radical humility — assume you're missing most of the relevant detail
- Extend more charity to experts — they're often navigating invisible complexity, not gatekeeping
- Use this insight to communicate better — your audience can't see what you see
- Plan projects with reference class forecasting and pre-mortems to account for unseen detail
- The insight connects to tacit knowledge — much of what matters in any domain can only be learned by doing
Final Thoughts: Why This Essay Still Matters in 2026
Nearly a decade after its publication, "Reality has a surprising amount of detail (2017)" is arguably more relevant than ever. We live in an era of confident hot takes, AI-generated summaries, and the illusion that information equals understanding. Salvatier's essay is a corrective.
The essay doesn't tell you to slow down or give up. It tells you to expect the unexpected complexity and engage with it honestly. That's the posture of every skilled practitioner, every good scientist, every effective leader.
If you haven't read the original essay, it's short — about 1,500 words — and worth your time. Then try to notice, over the next week, every moment where reality surprised you with a detail you hadn't anticipated. You'll be surprised how often it happens.
Start Applying This Today
Pick one area of your life or work where you've been frustrated by unexpected complexity. Instead of blaming yourself or the domain, ask: What details am I not yet able to see? Then find one person who has direct experience in that area and ask them what surprised them when they first started.
That single conversation will teach you more than any article — including this one.
Frequently Asked Questions
Q1: Who wrote "Reality has a surprising amount of detail"?
John Salvatier, a programmer and researcher, wrote the essay and published it on his personal blog in 2017. It gained significant traction in tech and rationalist communities and has been widely shared ever since.
Q2: Where can I read the original essay?
The original essay is available on Salvatier's blog. Searching "Reality has a surprising amount of detail Salvatier" will surface it immediately. It's short and freely available.
Q3: Is this related to the planning fallacy?
Yes, closely. The planning fallacy — our tendency to underestimate how long tasks take — is partly explained by the mechanism Salvatier describes: we plan based on the visible details, not the full complexity that only becomes apparent during execution.
Q4: How does this apply to AI and machine learning in 2026?
Very directly. Many organizations have discovered that deploying AI systems is far more complex than it appears from the outside — data quality, edge cases, user behavior, regulatory compliance, and model drift are all examples of "surprising detail" that only become visible once you're deep in implementation. The essay is practically a guide to why AI projects so often exceed their initial scope.
Q5: Can this insight be applied to personal relationships?
Absolutely. One of the most humbling applications of "Reality has a surprising amount of detail (2017)" is recognizing that other people's inner lives, histories, and motivations are vastly more complex than our models of them. This is a strong argument for curiosity over judgment in how we relate to others.
Top comments (0)