If your workspace looks anything like mine, your notes are scattered across five different apps. You’ve got environment variables stashed in Apple Notes, half-finished system architectures in a Notion board, API keys in a random .txt file, and an endless stream of saved Stack Overflow links you’ll never look at again.
When you are juggling student life, freelance builds, and personal projects, you don't have the time or cognitive bandwidth to hunt down that one database schema you wrote three months ago.
We try to fix this chaos by organizing our thoughts into elaborate folder hierarchies. But here is the fundamental problem: your brain doesn't work in isolated folders.
When you’re designing an architecture, you aren’t thinking in silos. You’re relying on associative networks. This is where a paradigm shift called "networked thought" comes in, and why I’ve moved my entire development workflow to a local-first app called Obsidian.
The Folder Fallacy
Every standard productivity app treats files as isolated pages. You write a document, put it in a folder, and it goes into digital cold storage.
But whether you are deliberately applying System 2 thinking to a complex software design or just mapping out a new automated pipeline, insights happen when unrelated concepts collide. When you trap your backend API endpoints in a different folder than your user psychology notes, you destroy their ability to interact.
Obsidian flips this. Instead of pages, your notes become nodes.
Meet Obsidian: Local, Fast, and Future-Proof
Obsidian builds a web of your thoughts. For a developer, the underlying architecture is a breath of fresh air:
100% Local & Yours: No cloud lock-in. No SaaS subscription to access your own thoughts. Everything lives locally on your machine.
Future-Proof Markdown: Every note is just a .md file. It's lightweight, universally readable, and perfectly suited for developer documentation. You'll still be able to read these files in 50 years.
Git-Friendly: Because they are just local markdown files, you can version control your entire second brain using Git. Push it to a private repository and you have ultimate, free data security.
Thinking in Links (The Core Mechanic)
The magic happens in how Obsidian connects information. By wrapping any word in double brackets, you instantly link notes together, like [[Diffusion Models]] or [[MongoDB Atlas Schema]].
As you do this, Obsidian automatically generates a visual Graph View.
Here is what this looks like in practice:
Let's say you are engineering a Python-based AI Image Detector. You create a note for extracting embedded credentials. Instead of burying it in a rigid "Python Scripts" folder, you link it to your broader notes on [[Machine Learning]] and [[Digital Forensics]].
Months later, when you are building a cross-platform CLI tool for open-source information gathering, those old notes seamlessly resurface. The ideas compound. One concept naturally connects to ten others, sparking architectural insights and workflows you never explicitly planned out.
The Ultimate Dev Environment
You don't need another web app to store your code snippets. You need an environment that scales with your technical knowledge. With over 1,000 community plugins, you can integrate Obsidian with your terminal, execute scripts, connect to your n8n webhooks, and customize it to fit your exact workflow.
It’s time to ditch the folders and build a system that actually thinks alongside you.
This is just the surface of what networked thought can do. I am currently documenting how I use Obsidian as a complete operating system for code, study, and life. Drop a follow for Part 2!
Top comments (1)
The biggest win with a developer notebook is preserving why a snippet mattered, not just the snippet itself. Code fragments age quickly; the decision, tradeoff, bug context, and "when not to use this" note are what make the knowledge reusable six months later.