How to Analyze Books like a Renaissance Scholar

Main ideas / lessons conveyed

• Deep reading is a skill most people are never explicitly taught.

  • Many people can “read words,” but fewer know how to read deeply, retain ideas, and extract themes that stick.
  • The creator describes learning this through years of struggle, trial and error, failing, and writing.

• Adopt a personal, adaptable system—don’t copy it blindly.

  • There’s no “perfect” universal method.
  • The system should be inspired by and then tinkered with to fit your brain, preferences, and goals.

• Use a simple 6-step workflow to analyze books.

  1. Book selection
  2. Book inspection
  3. Note taking
  4. Analysis
  5. Archiving
  6. Synthesis

• Purposeful reading should be driven by self-knowledge.

  • Pick books that excite you rather than following trends or hype.
  • Use two guiding questions:
    • What do I want to know most?
    • Who do I want to become (ultimate life purpose/goal)?

---

Methodology / system (detailed bullet points)

1) Book selection

• Choose books you genuinely care about (not what’s trendy, what “NPC gurus” promote, or what you feel pressured to “flex”).
• Let your reading be aligned with your interests so you’re not fighting an uphill battle.
• If you have many interests, narrow down using:
  • Question 1: What do I want to know? (prioritize what’s most urgent/interesting/pressing to you)
  • Question 2: Who do I want to be? (read in service of your intended identity/goals)
• The speaker’s example goals:
  • Improve writing
  • Read great books and share ideas (reviews/articles/videos)
  • Read the best historical “defining civilization” classics/masterpieces
• You can still read for fun (e.g., manga) as long as it matches your personal priorities.

2) Book inspection (before committing fully)

• Goal: avoid investing time only to discover you’re bored/confused.
• Spend ~5–10 minutes “flicking through” the book.
• Answer key questions:
  • What type of book is it?
    • Don’t assume purely from title/cover.
    • Example: Animal Farm might look like a simple novel about farm animals, but it’s also a political commentary.
  • What is the book actually about?
    • For clear books, it’s often obvious from category/blurbs.
    • For abstract/edgy books, inspect by:
      • Reading a few pages
      • Looking at the front and back material
      • Glancing at conclusion paragraphs to infer the purpose and main arguments/themes
• If it’s not for you, you save time; if it is, you start with foresight that makes analysis easier.

3) Note taking (during reading)

• Use notes to turn reading into an active conversation, not passive consumption.
• The creator contrasts:
  • Listening to a lecture passively vs.
  • Participating in a one-to-one conversation (notes force you to engage).
• Annotation approach (practical, not excessive):
  • Avoid over-annotating with “art kits”; keep it lightweight.
  • Highlight selectively: highlight only what stands out; if everything is highlighted, nothing is.
  • Underlining alone isn’t enough—notes should answer why it mattered.
• For better memory and usefulness, annotate with:
  • Your reason for the annotation (“it reminded me of…”, “it sparked a question…”)
  • Connections to other parts of the book or other books
  • Small conclusions/phrases that capture what you think
• Types of notes the speaker models:
  • Personal parallels (e.g., Gilgamesh’s development resembles Adam)
  • Questions that arise from controversial or surprising events
  • Occasional humor/“take notes for recall,” not only seriousness
• If notes feel like too much, the creator suggests boiling it down to:
  • “As you read, write what you think to help you think.”

4) Analysis (slow, thorough “second pass” using your notes)

• When you finish the book, go back to page 1 but don’t re-read everything.
• Instead:
  • Ignore the text except where your notes/highlights point
  • Pause on underlined/annotated sections and expand them
• The creator uses a tool/workflow in Obsidian:
  • Create a source note per book/article/video
  • Record:
    • Page numbers
    • Copy key passages/quotes (as the reference anchor)
    • Write the creator’s ideas in their own words
    • Elaborate, ask questions, connect themes
• Key principle: your short annotations become the springboard for more concrete writing.
• The creator emphasizes that this step takes much longer than reading, but produces deep satisfaction.

5) Archiving (turn source notes into an expandable knowledge library)

• Purpose: build a lasting archive so you can revise or reuse ideas later without re-digging.
• Central concept: Atomic notes
  • “Shipping containers of the note world”
  • Each atomic note represents one important idea
  • They are short and stored all in the same place (same folder), not scattered by topic
• Rationale for single-location storage:
  • Folder-based systems make it hard to find and connect ideas.
  • Connections are what produce new insights (“networks of existing ideas”).
• The creator offers organization aids:
  • Indexes/contents so you don’t lose track.
  • Tags and references to maintain order even if notes are all stored together.
• How to create atomic notes (criteria: only what deserves permanent capture):
  • (1) Standout ideas that either:
    • Transcend the specific source note, or
    • Are deep enough to become standalone themes
  • (2) Recurring themes across the book
    • Gather many related passages/angles into one atomic note
  • (3) Your own thoughts
    • You can write exploratory questions or hypotheses that arose while reading
• Typical length:
  • Often a few sentences to ~2–500 words
  • Preferred format: mini-essays (optional supporting mention of a separate video about that format)
• Ongoing effect:
  • Notes accumulate (“compounds over time”) into a personal knowledge bank.

6) Synthesis (cross-book understanding like a Renaissance scholar)

• Use atomic notes from multiple books to draw new insights.
• In synthesis you:
  • Link atomic notes across sources
  • See clearer pictures/angles you couldn’t see from one book alone
  • Detect disagreements/inconsistencies across books
  • Fill in gaps because no single book covers everything
• The speaker frames expertise as:
  • Achieved by repeatedly connecting ideas across multiple works.

---

Practical linking workflow (how to find what connects)

• When you finish an atomic note, look for related notes in:
  • The same book
  • Other notes you already wrote
• Linking methods discussed:
  • Use clever titles including major terms so search can retrieve them
  • Browse by tag and scan note lists
  • Use graph view to visually cluster related notes
• Limitation acknowledged:
  • The network doesn’t have to be perfect; you’ll miss some connections.
  • Even 1–2 good links are valuable.

---

Source(s) / speakers featured (as stated in the subtitles)

Featured speaker (primary source)

• The video creator / narrator (unnamed in subtitles)

Referenced external sources (people/books/topics)

• George Orwell (Animal Farm)
• Jordan Peterson (lecture related to meaning and responsibility)
• Jordan Peterson (referenced again via meaning/purpose connection)
• Adam (Biblical figure) (used as a comparison point)
• Sebastian J. Y. Yer (Sebastian Yer) — Tribe (anthropology/psychology book; as referenced)
• Consensus (research tool; the video states it is a sponsor)
  • Research assistant / “consensus as a personal research assistant” (no individual person named)
• Epic of Gilgamesh (the text the narrator uses as a running example)
• Jordan Peterson (again, via a past lecture reference)
• “Jordan petson” (subtitle spelling) = Jordan Peterson (same person)
• Nuance / class / science history / school (not specific sources; general references)

Also mentioned / example names or terms (no clear “speaker”)

• “Waterstones,” “Bars & Noble” (bookstores)
• “Reddit,” “Instagram,” “Google Scholar” (platforms/tools referenced)