Comment by mikestorrent
15 hours ago
There's a great meme with the classic intelligence bell curve setup where the "grug" and the "elite" sides both use a plain text file with their own ideas of how to do things, and only the "midwit" in the middle is using a huge pile of tooling to accomplish roughly the same thing.
I too went through the phase of using Dendron and Obsidian as well as more common todo list tools (and tickets)... and here I am back at Apple Notes, whose sole advantage over a text file is that it has enough capabilities to store a screenshot. That's all I really needed. My notes are like the classic notebook: a lot of the time it's write-only, a lot of the time it only has to be able to be understood for a week or two before the information is too old to matter anyway.
Don't overthink it.
Why is capability to store a screenshot useful in a to-do list?
I'm not the person you're replying to, but I have several TODO items on my current project for fixing HMI screens. Those will be performed by one of my teammates. I could easily embed images into the org-mode document I use.
Unfortunately for him, the HMI is air-gapped so getting screenshots is cumbersome. He'll have to make do with my notes.
TODO: Fix this <screenshot of thing>
Takes like two or three seconds to add; then I continue doing what was more important, and flip back to this with a decent context jumpstart later.