@nickanderson That approach looks cool.
How do you deal with your TODOs then?
*Not* scattering them doesn't automatically improve things, I can tell :) I refile my TODOs in a handful of org files, but it's still way too many to make the TODO agenda work for me at all. I would have to separate "to-actually-do" from "this-is-doable-in-theory" (which both are different from regular org content headings)
I can only imagine it's even more the case with spreading TODOs through org-roam
@ctietze In reality, currently I don't have anything or really try to wrangle them. I schedule things in my calendar if I need to box time and I don't yet try to pull my calendar in to agenda either. I simply have a daily log that contains my work for the day and where I clock time. It links to other various things. When something becomes important enough and or interesting enough I work on it.
@ctietze I don't even have many todos anymore. It was an ever growing list that just worked against me psychologically. But I still want to use agaend, it seems so powerful. Using agenda based on files that contain nodes with created property from some period seems like it could help both with parse time and horizon. Probably usually I don't care about the three year old todo that isn't done because if it were important it would have resurfaced and I would have done it.
@ctietze in fact using that method I found several todos that I had done, but never marked them. But likely I had logged that work in a daily file probably the same day or next day around the created time.
@nickanderson Hmm I see! FWIW, my approach doesn't work for me 'psychologically' either. I usually work on some (creative) task during the day and complete implicit or explicit todo's along the way, but usually never sit down and check which TODO I should tackle next