Why you NEED to learn Obsidian // EP1 Mastering Obsidian

Bi-directional linking is the core shift Obsidian pushes: instead of filing notes into folders and hoping you’ll remember where they live, notes become connected directly to other notes—so future writing starts with a web of prior thinking. The practical payoff is that when a topic comes up again, the system surfaces all the related notes instantly, letting people build on accumulated research rather than starting from zero. That matters most for anyone who takes notes over time but rarely revisits them, because folder hierarchies often hide the relationships that make notes valuable.

The case for Obsidian rests on four reasons tied to bi-directional linking. First is community plugins: a large ecosystem of add-ons can extend the workflow without paying for upgrades, including tools like the Kindle highlights plugin that imports Kindle highlights into an Obsidian vault and syncs them on demand. Second is future-proofing. Obsidian uses Markdown and stores work in a local vault rather than a proprietary server format, so notes can be moved or backed up to services like Google Drive, iCloud Drive, Dropbox, or local storage. Third is privacy and control: because the vault lives on the user’s chosen storage, backups and security are under the user’s control. Fourth is price: Obsidian is free for personal use.

Who benefits most is framed broadly but with emphasis on knowledge work. Non-fiction writers, research analysts, content creators, and other knowledge workers are singled out because they continuously accumulate information and need notes that grow into connected ideas. The goal isn’t just storage; it’s strengthening and expanding thought over time so those connections can be reused in future projects.

The walkthrough then shows how Obsidian is set up and why its structure supports the linking approach. Creating a vault establishes where Markdown files live locally, with the option to place it on iCloud Drive for syncing across Apple devices. The interface supports creating new notes quickly (including via Command N), and notes appear as Markdown files in the vault directory. While folders are still possible, the emphasis is that they’re optional rather than the organizing principle.

Settings highlight one key recommendation: enabling automatic updating of internal links so links remain consistent as notes change. Customization is acknowledged as powerful but risky for focus—people can lose days chasing plugins and themes. Plugins are split into core and community categories, and community plugins can carry malicious code risk; safe mode and popular-plugin selection are mentioned as practical safeguards.

The bi-directional linking example uses square brackets to create links between notes. Terms like “intermittent fasting,” “keto diet,” and “meditation” become their own linked notes, and graph view reveals how a single concept connects to multiple sources. Over weeks and months, those links accumulate, so searching for a topic later surfaces dozens of connections—turning note-taking into an engine for future drafts, content ideas, and well-researched writing.

Finally, the episode closes with essential Markdown basics: headers via hashtags, edit/preview toggling with Command E, and simple formatting like bold and italics using underscores and asterisks. The message is clear: once linking and Markdown fundamentals are in place, the vault can grow into a navigable knowledge network rather than a static archive.