Example of topic vs object tags to make more sense of tagging practices
I shared this on my blog earlier this week:
So I talked with a fellow iOS developer about tagging recently, then overhauled a note I found by accident and shared this as an example.
The gist is:
- I increased specificity of tags. The general
#nsimageon macOS, which are actual types in the macOS API.
- I removed the topic tag
#appkitwhich doesn't tell me anything interesting here.
Why is the object tag
#appkit useless now? Almost all my programming notes are about macOS and thus
#appkit, the macOS UI API framework. So it doesn't help find anything, and it'd produce so many notes that it becomes useless. Thousands, if applied consistently!
There are notes about the AppKit framework as a topic. These stay put, of course!
The thing is: for my very first notes on programmatic image manipulation, it sounded sensible to use a tag like
#image. After all, I did not expect to need specificity here at all: "something with image in Appkit" sounded good. But with expertise, I need
NSImage-related resources, and I can name contexts better. Like embedding images in text views, as wirh The Archive
All notes are malleable, so no problem.
By the way, new notes on similar topics I tag with the very specific API titles right away, e.g.
#nsimage for image stuff on Mac. This changed in the past couple of years and I don't have to think about this, at all. I believe it felt similar back when I used the """bad""" tag. So chances are I could discover even more specific tags in the future and find the current one lacking At the moment, it's the best topic tag I know to describe this.
Author at Zettelkasten.de • https://christiantietze.de/