CHAPTER 19
About the Author
Read It
The "About the Author" page looks like a resume: startup experience, a popular blog, a home in Kansas City, a sandwich-making hobby. But the real question isn't "Who is Eric Jorgenson?" It's "Why should I trust this person to curate Naval's ideas?" The answer is layered. At the base is hands-on practice—building a startup, making product decisions—which gives him the judgment to know which ideas are actually operational. Above that is communication skill: a blog with a large readership proves he can take complex ideas and make them clear without dumbing them down. At the top is personal credibility: the willingness to include his own life details, even the trivial ones, signals that he's not hiding behind a professional persona. He's a person, not just a compiler. Each layer answers a different version of the trust question, and only together do they justify the book's existence. The chapter closes the loop: these ideas aren't just curated; they're lived.
Open full image ↗Draw It
Resume-style text flattens everything into a list of facts. But the facts serve different functions. Practice establishes domain judgment. Writing establishes communication ability. Personal details establish authenticity. If you map them as parallel items, you get a bio. If you map them as layers, you see a credibility stack: each level supports the one above it. The visual choice was to separate the layers, because that's what lets a reader decide how much weight to give the author's voice. A person with practice but no communication skill can't explain; a person with communication but no practice can't judge; a person with both but no authenticity can't be trusted. The layers are not interchangeable.
Rethink It
In technical communities, we often judge an author by a single metric: GitHub stars, job title, or follower count. But those are flat signals. A Staff Engineer's blog is worth reading not just because they write good code, but because they've survived real system failures and are willing to write about the ugly parts. The credibility stack applies: practice, expression, honesty. When I evaluate a technical author or speaker, I try to assess each layer separately. Someone with deep practice but poor expression may still be worth reading if I can decode the substance. Someone with slick expression but shallow practice is dangerous. The cost of flattening the layers is trusting the wrong voices.
Take It With You
A bio's value is not the facts it lists. It's the basis it gives you for deciding how much time to spend on this person's ideas. Trust is layered, and each layer needs its own evidence.