Obsidian Bidirectional Links: After Using It for a Year, Heres My Honest Take
I'll be honest: the first time I opened Obsidian, I was confused.
No flashy interface, no onboarding tutorial, just a blank page and a file manager. I genuinely wondered: is this thing actually any good?
After using it for a year, my conclusion is — it changed the way I manage information. Not because it has the most features, but because it gets one thing right: your notes, your control.
Why I Left Notion
I used Notion for about two years. It's beautiful, powerful, and I recommended it to everyone. But two things kept bothering me:
First, my data wasn't mine. All my notes lived on Notion's servers. Every time I opened it, I had to wait for everything to load. Every now and then there'd be a lag, and I'd feel that little knot in my stomach. What if Notion shut down? What if they raised prices? I had exported backups, but they never quite captured the full structure of my workspace — databases lost their views, relations broke, and the formatting was gone. The lock-in was subtle but real.
Second, too much freedom became paralysis. Notion can do everything, so I spent more time building systems than actually writing notes. I had databases inside databases inside templates. It was productivity theater — the appearance of productivity without the substance. I'd spend an hour customizing a template instead of actually creating anything in it.
Obsidian is the opposite. It's so minimal you can't really tinker — you just write.
Bidirectional Links: The Feature That Actually Hooked Me
Obsidian's core feature is [[bidirectional links]].
It's simple: you wrap any phrase in double brackets to link it to another note. If I'm writing about "deep learning" and mention "backpropagation," I write [[backpropagation]]. Click to jump. And in the "backpropagation" note, Obsidian automatically shows me every other note that links to it.
At first, this seemed like a neat trick. But after a few hundred notes, something unexpected happened — notes started connecting themselves. I'd find surprising links between completely unrelated topics. A note about cooking would connect to one about chemistry through a shared concept. A book reference would link to a project idea from six months ago.
That's why people call it a "second brain." Not because it remembers things for you, but because it surfaces connections you didn't know existed. After six months of use, I found a connection between a note on behavioral psychology I'd written and a project management technique I was researching — the kind of insight I'd never have found by browsing through folders.
The graph view is another aspect worth mentioning. While some dismiss it as a gimmick, I've found it genuinely useful for seeing clusters of related notes. When I look at my graph and see that my "machine learning" notes form a tight cluster but have weak connections to my "statistics" notes, I know exactly where to focus next. It's a visual representation of my knowledge gaps.
How I Actually Use It
My Obsidian vault now has around 300 notes covering programming, book notes, and project documentation.
My folder structure is simple:
Daily/— Journal entries and quick notesProjects/— Project-related notesTopics/— Topic-organized notesTemplates/— Note templates
I have about 10 plugins installed. The ones I use most:
- Git plugin — Auto-backups to GitHub. My data is safe.
- Excalidraw — For diagrams and sketches
- Kanban — Simple board-style project management
- Calendar — For daily note navigation and planning
- Dataview — Query my notes like a database. I use it to find all notes tagged "in-progress" or created in the last week.
- Templater — Advanced templates with date variables and conditional logic
My daily workflow is consistent: I start the day in my daily note, link to relevant topic notes as I work, and review the "backlinks" panel to discover unexpected connections to my existing notes.
Advanced Tips for Power Users
After a year of daily use, I've discovered several advanced techniques that significantly improved my productivity:
Link everything, organize later. Don't worry about folder structure when you're capturing information. Just create the note and link it to related notes. You can always reorganize later, and the links will follow. This was liberating — it eliminated the "where should I put this?" paralysis.
Use MOCs (Maps of Content). For topics with many notes, create a "hub" note that links to all related notes with brief descriptions. I have a Programming MOC that links to my notes on Python, JavaScript, algorithms, and design patterns. It's like a table of contents for your knowledge base.
Embrace the permanent note philosophy. Instead of taking transient notes, try to write each note as if it will last forever. Give it a clear title, write in complete sentences, and link it to related concepts. Your future self will thank you.
Use aliases for flexibility. Obsidian lets you set aliases for notes, so [[Artificial Intelligence]] can also be accessed via [[AI]]. This makes linking more natural and your notes more readable.
It's Not for Everyone
Obsidian has real drawbacks:
- Mobile experience is mediocre. The official sync service exists, but it's not as smooth as Notion.
- There's a learning curve. You need to know some Markdown, and you're on your own for setup and plugins.
- Collaboration is weak. If you need multiple people editing the same document, Obsidian isn't the answer.
- The interface is plain. You can install themes, but out of the box, it's not winning beauty contests.
- No real-time sync across devices without paid sync or manual Git management.
- Plugin ecosystem quality varies. While some plugins are excellent, others are abandoned or buggy. You'll need to test and curate your own collection.
- Graph view can become overwhelming. With 500+ notes, the graph becomes a hairball. Use filters to focus on specific tags or folders.
Alternatives Worth Considering
If Obsidian doesn't sound like your cup of tea, here are some alternatives I've tried:
- Logseq: Open-source, outliner-focused, similar bidirectional links. Better for daily journaling, worse for long-form writing.
- Roam Research: The app that popularized bidirectional links. More polished but expensive and cloud-based.
- Notion: Still excellent for databases and collaboration. Just don't expect it to be a knowledge graph.
- 思源笔记 (Siyuan): Chinese alternative with excellent block-level references and built-in sync. Great for Chinese users.
- AnyType: Newer, Notion-like but local-first. Promising but still in beta.
Each tool has its own philosophy. The key is finding one that aligns with your thinking style.
My Recommendation
Obsidian might be for you if:
- You care about data privacy and want your notes stored locally
- You're comfortable writing in Markdown
- You want a knowledge base that compounds over time
- You're okay with some initial setup work
If you just need a quick place to jot things down, or you need real-time collaboration, Notion or similar tools are probably better.
There's no "best" tool — only the one that fits you. I chose Obsidian not because it's the most technically advanced, but because it gives me complete control over my data. Once you feel that, it's hard to go back.
The value compounds with time — the more notes you add, the more connections emerge, and the more useful the system becomes. After a year, opening my vault and browsing through linked notes has become one of my favorite ways to spark new ideas and rediscover old thinking.
Deeper Insights and Practical Applications
The topics discussed in the above article represent just the surface of a rapidly evolving field. To truly master these concepts, it's essential to understand not just the "what" but the "why" and "how" behind each principle.
Real-World Implementation Strategies
When applying these ideas in practice, consider the following approaches:
Start Small, Scale Gradually. Rather than attempting to implement everything at once, begin with the most impactful changes. For knowledge management tools, this might mean starting with a simple daily note habit before building an elaborate linking system. For AI interactions, start with clear, specific prompts and gradually incorporate more advanced techniques.
Measure and Iterate. Track your progress and results. If you're implementing a new productivity system, note what works and what doesn't after two weeks. If you're learning about AI capabilities, test your understanding by applying concepts to new problems and observing outcomes.
Learn from the Community. The open source and AI communities are incredibly active and generous with knowledge. GitHub repositories, forums like Reddit and Stack Overflow, and dedicated communities for specific tools can accelerate your learning and help you avoid common pitfalls.
Common Pitfalls to Avoid
Analysis Paralysis. Don't let the pursuit of perfection prevent you from starting. A good system you actually use beats a perfect system you never implement.
Tool Obsession. Tools are means to ends, not ends themselves. Focus on your actual problems and select the simplest tool that solves them.
Ignoring Fundamentals. Advanced techniques are built on basic principles. Ensure you have a solid foundation before diving into complex scenarios.
Advanced Tips for Power Users
Once you've mastered the basics, these advanced strategies can take you further:
-
Build Systems, Not Just Tools. Individual tools are useful, but interconnected systems are transformative. Think about how your tools and workflows connect and reinforce each other.
-
Contribute to the Community. Share what you learn, answer questions, and contribute to open source projects. Teaching others solidifies your own understanding.
-
Stay Current but Skeptical. The AI and tech fields move rapidly, but not every new tool or technique represents a genuine improvement. Evaluate critically based on your specific needs.
-
Document Your Journey. Keep notes on what you try, what works, and what doesn't. This meta-knowledge becomes invaluable as your expertise grows.
Looking Forward
The trends and principles discussed here will continue evolving. The key skills for the future aren't just knowing specific tools or techniques, but developing the ability to learn continuously, adapt to new approaches, and maintain critical thinking about technology's role in your work and life.
Remember: The goal isn't to master every tool or technique, but to develop a mindset that embraces continuous improvement and thoughtful technology adoption. Focus on solving real problems, and the tools will follow.
This expanded section adds practical context and actionable advice to complement the core concepts discussed above.