Using ZKM for learning about a software
Hey!
I'm starting a new job, and I have to learn some new software. I want to put what I learn into my Archive.
I don't know why, but it feels awkward to me to go through the software's documentation and start writing notes about the different features. Intuitively it seems at odds with ZKM. But, I'm don't think it actually is.
But, is that how you'd do it also?
Start with a structure note, and start to branch off into these different features within the software, writing notes about the different features?
Thanks for you thoughts in advance!
Howdy, Stranger!
Categories
- 3K All Categories
- 152 Research & Reading
- 692 The Zettelkasten Method
- 7 Knowledge Work
- 100 Writing
- 464 Software & Gadgets
- 154 Workflows
- 730 The Archive
- 15 Plug-In Showcase
- 88 Resolved Issues
- 225 Projects Logs and Journals
- 83 Project: Zettelkasten.de
- 53 Critique my Zettel
- 171 Random
- 373 Introduce Yourselves!

Comments
I'm documenting my journey through what is probably the simplest yet most powerful/annoying/lovable piece of software, Emacs. So yes, I can say it helps
Here's my first one for reference:
# 201803231421 Emacs configuration paths #emacs #configuration Global Emacs configuration is located here: ~/.emacs.d/init.el Open it in an Emacs buffer with `C-x C-f`.Or manipulate what I see on screen, my 2nd note, because I couldn't remember for the life of me how to remove all these window splits, gah!
Note the very bad tagging ;(
Another example: DaVinci Resolve! I'm not a video editor so the industry standards don't mean anything to me.
You see these are all very isolated notes. There's no link to be seen. That is, I believe, because I had to start with something. Eventually, structure notes emerged about navigating around in Emacs, about file manipulation, etc., and then these atomic notes above were used there. So they're not orphans anymore
Author at Zettelkasten.de • https://christiantietze.de/
Very helpful feedback.
Thank you!