Show HN: Org-Supertag
github.com
Enhance org-mode tag system, borrow idea from tana.
github.com
Practical example? You can be annotating a PDF, while having executable code blocks in different languages, e.g., you can run http or sql query, then pass the results into a python, javascript or shell scripting block, and then output the final result into a diagram. So, you'd be reading the book, taking notes and mess around with practical code snippets at the same time.
I have tried so many different note-taking apps, philosophies and techniques over the years. Nothing even comes close to what I can do today in Org-mode. It totally shatters everything else and kicks the shit out of the ballpark.
I'll just say that even to another "expert", you didn't explain what's so great about this annotation workflow.
As for the annotation workflow, well, I guess you just don't need it. When you decide to start writing notes while reading books, I'm sure you'll be able to figure it out. For now, just create a TODO item with a deadline, it will keep showing up in the Agenda, but I don't have to explain, that part you know already.
I prefer these outlined based notes tools ( org mode, roam, Tana ) over the document based ones (Obsidian, etc) or db ones ( notion ).
It feels like a personal taste thing. I naturally think in lists and to-dos.
They are looking for a name for the concept, so suggestions are welcome!
But I've tried to dive into Org mode twice in the past five years, each time committing a few weeks to learning it. However, I eventually gave up and returned to Logseq. The steep learning curve was the biggest hurdle for me. Between understanding Lisp, figuring out and choosing between all the possible configurations and workflows, memorizing the keyboard shortcuts, and working through YouTube tutorials, the friction and mental load were just too high.
Logseq, on the other hand, provided most of the features [1] I needed while keeping the barrier to entry much lower - far, far lower than Emacs. But LogSeq is by no means perfect; I fear it will become bloated at some point (e.g., I have no interest in flashcards and spaced repetition learning)
[1] Outliner; data kept local; journal; simple task management; easy to insert quotes, code snippets, images; backlinks; possible to attach files
M-x === hit x and the ESC key (of all things) at the same time?
If you aren't an emacs person, it is not going to be a fit.
Workflowy is a pretty easy-to-use web version of the outline part, which requires zero setup and the other features of org-mode I never got into. Other things extend beyond this into the PKM space ( Roam, Tana, etc ).
Also, Zettelkasten is an interesting thing, but more as a curiosity, some process that worked for a specific researcher in nineteen dickey two, not as some process you should use.
For me, the big great outliner was workflow. Roam improved on that, and things improved for Roam.
Zettelkasten is just an idea, and a great one. I don't know what you think it is, but all these apps - Obsidian, Roamresearch, Logseq, Org-roam - are based on that idea.
The goal of my notes is so far from this that I found the ideas interesting but unrelated to how I use Roam, etc.
I was used many tools, include Workflowy and Roam. For me, org-mode & Emacs is the best tool of all, no tool can compare.
Sure, learning Emacs and Org-mode is quite some journey. But it's absolutely worth the time and effort.
I even try different new things from time to time - out of curiosity, and because so many times before, I have felt like being stuck in a bubble. And so far, I have not found anything much better than Org-mode.
However, org-supertag is database-based, storing both the content and the relationship mappings in the database.
Saying that Org-roam is DB-based is like characterizing any codebase hosted on GitHub as "written in git". Even though, speaking pedantically, that's true; it still would be nonsensical.
Publishing to MELPA although is a fairly simple process, it does require certain steps and of course the vetting and approval. Often it takes long time. Sometimes (for various reasons) authors may decide not publish at all.
Am I missing something on going straight to applying my knowledge, after having found a solution to whatever problem I'm facing from a variety of sources, and not writing down many notes outside code comments/README.md ecc..? E.g: I'm currently building a mobile app with flutter, would you guys suggest that I log what I'm learning, even considering it's pretty basic stuff due to the fact that it's my first encounter with flutter/dart?
Now that I think about it, writing notes during the process could perhaps help me have more material for my blog posts
1. General knowledge: Anything I want to be able to look up again, for me mainly how to do certain tasks in software, which is things like keyboard bindings, steps to achieve a result (e.g., something like "remove the background from a photo"), and flags for a command line program. I also add more abstract things, like computer science, and music theory concepts, but I find these concepts are usually easier to recall from memory once you know them (I've read before that memory works like a web, so if you're attaching new concepts to existing concepts, they'll be easier to remember), so I don't have many notes like that.
2. Projects: Tasks related to a project, and things I've learned along the way. For example, if I'm diagnosing a bug, maybe I found an important code snippet, so I'll cut and paste it to the project file. Also useful commands, e.g., if there's a single test I'm working on, I'll save the command to run just that test in isolation.
The general principle here is I usually find it easy to remember if I've ever done something before, but hard to remember exactly how to do it. (Research indicates that if something doesn't fit into the web, then if you don't do it enough, you won't remember it, so the notes compensate for that.)
I find this helps me stay in flow because just looking something up quickly from my notes is much less disruptive than searching to find it again (or trying to think to reconstruct it). If you don't mind searching again later for something you know you once figured out, you probably don't need notes, but if that drives you crazy, like it does for me, than notes are helpful. For me, it feels like I'm constantly expanding the number of things I can do easily without having to depend on my memory, which I know from experience is fallible for these tasks.
It's similar for context switching between projects, when switching tasks, being able to look at your note for a project, and being able to see both exactly where you left off, and documentation of everything you've learned so far, makes it easier to move forward again.
Logs are meant to serve as a labnote book. Each entry is saved in a daily journal & with a date and simple description header. What I'm doing, why, how its going, checklist, etc. Basically a dumping ground for everything I could possibly have a use for re-using later. This help eliminates entire categories of notes(e.g. call with mechanic), and give you a chance to leverage smaller notes with backlinks to the individual experiences using it. The effort to keep notes evergreen is very difficult when the content keeps changing.
I used to spend a lot of time, thinking how should I organize my notes? Tried many different methods - categorizing them; grouping them by dates - years, months, days; putting them in multiple files and folders; using a single file with many (collapsible) headings, etc.
After switching to Zettelkasten method (I use Org-Roam), I realized - whenever I write any note, the only question that I really need to ask: "in what context should I re-discover this stuff later?".
A practical example: I would be discussing a session-related security vulnerability with my teammate, let's call them Jimmy. I would start a note with a meaningful title. Then add links to [[Jimmy]] [[session]] [[vulnerabilities]]. For simplicity, let's assume I already have these nodes in my system. 'Jimmy' is a node that has all the info about my teammate, their role, their contact info, etc. The node may also have its own tags, e.g., [[front-end-team]].
Now, months later, whenever a similar thing comes up, I wouldn't be scratching my head thinking "haven't I discussed that with Jimmy last year in October? Let me go through my October notes...". No, I would open Jimmy's node then lookup for all the backlinks and surely, I would find the relevant notes. I may even forget that I spoke to Jimmy, then I would find the notes through other nodes - [[front-end-team]] [[vulnerabilities]] [[session]].
I tried Org mode and used it for a year or two. I liked its integration of notes and task tracking. The Org Agenda works well. Ultimately I found it a bit chaotic to have tasks scattered amongst text files though. I acknowledge that I probably could have made Org work for this and my current solution (Omnifocus) is better in some ways, worse in others.
For the notes though, I just write plain text notes using Windows Notepad or Mac TextEdit and I put them in an appropriate folder. I have various folders - some for "projects" and others for "reference". I like the folders because I can put other things in them, such as PDFs, emails, spreadsheets, etc. Sometimes I have a single text file for a project that has chronological notes; other times, it's appropriate to add additional files to capture particular ideas, lists, etc.
The note-taking apps don't wind up doing much for me.
So I guess that means you hardly reuse any of those notes at all? I just can't really imagine the process of having to fish for some creative ideas from those buckets.
Years of experience has taught me that relying on loose tagging webs and searching mechanisms and fancy tools does not work for me, not for notes, not for emails, not for anything else. I organize things into nested hierarchies. This takes maintenance, but so does maintaining tag webs and using the tools to maintain and mine them.
For something that espouses some of these principles (though I do not use this system):
* Stop doing stuff in that field for months and have previously processed notes to reload in your head when you come back.
* Give feedback to maintainers on what worked/what didn't when you entered their ecosystem.
* Communicate to newbies how you overcome X problem when learning Y. Not everyone may have your particular insight. You could roll it into a blog post or other communications.
* Provide stepping stones for you to relate other frameworks and languages back to what you've already seen and know, to solve challenges in different domains.
I find that most more specific ideas for using the data come at random periods throughout my life. The questions are usually non-obvious when just staring at the data. I write them down as little notes themselves and come back to them when I have interest/motivation.
* Reminders
* Checklists
* Idea collation
* Fleshing out and prioritizing personal tasks
* Reference notes - e.g. passport number, tax numbers, frequent flier numbers, anything else I might want to input into a form one day.
* Calendar
* As a place to draft emails/letters/documents.
There's so much crossover between all of these things that it helps to keep them all together.
I wonder what would tagging get me here beside just showing up in the node search dialogs?
Would be interested to hear how people are getting on with Tana (https://tana.inc/), the tool from which this idea was borrowed.
Someone is looking into it now.
You can go through the back-door currently here: https://app.tana.inc/create-account (currently requires credit card to get in directly, but you can cancel it directly after).
Also, briefly checked https://tana.inc - which inspired the package, chuckled at: "The world's most powerful notes", and got the same question: "How is it more 'powerful' than Logseq, Obsidian, Org-Roam?"
Your words suggest that you haven’t looked into org-supertag.
To me, a long-time Org-Roam user, "TODO" is just adding a link to an org-roam node with the same name - which, again, after reading the description of the package, kinda, sorta feels like "pretty much the same idea". If you want to avoid unwarranted criticism (which my original comment was not), I suggest perhaps try explaining it better. I'm still not sure how org-supertag can complement Org-roam and Denote workflows.