My Notes Were Getting Scattered
I take a lot of notes when I study.
The problem is that my notes were starting to end up everywhere. Some were in PDFs. Some were in Word documents. Some were in screenshots. Some were saved as bookmarks. Some were in folders that made sense at the time but were hard to find later.
That became a problem because I am learning a lot of different things.
Linux. Networking. PowerShell. Bash. Python. GIS. Cybersecurity. Windows Server. Databases. Web development. SCADA.
Each topic is different, but they also connect to each other. I needed a better way to keep track of what I was learning.
That is why I started using Obsidian.
Why Obsidian Works for Me
Obsidian is a note-taking app, but what I like about it is that it does not feel too complicated.
My notes are saved as Markdown files. That means they are plain text files stored in a folder. I am not locked into one app forever. I can back up the files, move them, or sync them with something like Dropbox.
I like that because it feels simple and practical.
For technical learning, plain text also makes sense. A lot of IT work already involves text: commands, scripts, logs, notes, checklists, and configuration files.
So Obsidian fits the way I am trying to learn.
The Zettelkasten Method
One note-taking method that works well with Obsidian is called Zettelkasten.
Zettelkasten is a German word that means “slip box” or “note box.” Before computers, it was a box filled with small paper notes or index cards.
The idea is simple.
Instead of writing everything in one long notebook, you write smaller notes. Each note focuses on one idea. Then you connect that note to other related notes.
The method became well known because of Niklas Luhmann, a German sociologist who used this system for his research and writing. His notes were not just stored away. They were connected to each other, which helped him build and develop ideas over time.
That is the part I like.
It is not about making perfect notes. It is about making useful notes.
Why This Helps with IT Learning
A lot of technical topics are connected.
Linux file permissions are not just a Linux topic. They also matter in cybersecurity, scripting, server management, and troubleshooting.
PowerShell is not just a scripting language. It connects to Windows administration, Active Directory, automation, reporting, and security.
GIS is not just about maps. It connects to databases, web apps, servers, Python, and field operations.
That is why I do not want my notes to sit alone in separate folders. I want to connect them.
With Obsidian, I can create a note about one topic and link it to another topic. Over time, those links help me see how things fit together.
I Want the System to Stay Practical
I am not trying to build a perfect note-taking system.
I do not want to spend more time organizing notes than actually learning. I do not need a complicated setup with too many plugins, templates, and rules.
For me, the system only needs to answer a few simple questions:
Can I write down what I learned?
Can I find it later?
Can I connect it to something related?
Can I use it when I am working on a script, troubleshooting a server, studying GIS, or planning a project?
If it helps me do those things, then it is working.
Smaller Notes Are Easier to Use
One thing I am trying to do is write smaller notes.
In the past, I would sometimes create one big note for a topic. That sounds organized, but it can become hard to use later.
A huge note can turn into a junk drawer.
The Zettelkasten method pushes me to keep notes focused. One note should explain one idea.
A note about SSH keys does not need to explain all of Linux.
A note about DNS records does not need to become a full networking book.
A note about ArcGIS Enterprise does not need to include every admin task.
Smaller notes are easier to update, easier to link, and easier to understand later.
Learning Is Not Always Straight
Learning does not always happen in a straight line.
Sometimes I read something and only understand part of it. Then I see it again in another book, another video, or a real work situation, and it starts to make more sense.
That happens a lot in IT.
A command may not make sense the first time I use it. A networking concept may feel abstract until I troubleshoot a real issue. A GIS server topic may become clearer when I connect it to databases, web services, and security.
Obsidian gives me a place to keep those pieces together.
My Setup Is Simple
Right now, I want my setup to stay simple.
I need notes for topics I am learning.
I need links between related ideas.
I need a place for PDFs, references, commands, scripts, and project notes.
I need a system that helps me learn, not a system that becomes another project by itself.
That is enough for now.