I am rethinking my JD structure a bit now, and there has been a recurring problem I can’t grapple with alone.
So… I decided to visit my lovely friends on the forum; the dilemma is this:
I need at most ten life buckets, some areas may need no files, some no notes, and some no tasks, and some with tasks may need no notes or files.
I don’t store many files, not at all. I work a lot with notes and tasks, though. But notes… they don’t need any folders, and I just use links, tags, MOCs, etc.
I also realised that, really… it would sort of be best if each thing, namely: notes, files, and tasks, had its own optimised version of decimals, but then, that defeats the purpose of having it consistent across everything!
Should I just be fine with, areas being almost completely empty in files? I don’t need ‘files’ about PKM or Productivity, this stuff lives in my notes and tasks.
It seems like… I just have to embrace some chaos. Fine, I’ll have ten digits for something that is almost empty, so empty it does not need categories… but decimals can be extended, so that’s not a problem!
Or, for instance: PKM and Productivity are best to separate in notes and tasks, of course, as areas but in files… they are intermingling… so I created
50-59 PKM & Productivity but then, it’s not really consistent… but is that really a problem now?
I think I’m trying to make it too organised and can’t embrace a little bit of chaos. But chaos is inevitable!
So, I’ll probably just let go on that perfectionism and if required, have 10 areas in files, and even 20 in my tasks, why not? If 50-59 PKM & Productivity can live together harmoniously within files, but in tasks, better not, I’ll just divide them up there!
And notes… I don’t need folders for notes. I may just create an entirely different JD structure than that of my files and tasks in my vault, I’ll just use three digits instead of two and… voila! (to organise my existing folders in vault a little bit better)
So, to summarise, what I think I’ll do (and I really really want your thoughts on this!)
Embrace some chaos and inconsistency by tailoring my needs for each ‘sphere’; my system is not so big that it can cause any real issues. (I most likely took ‘make it consistent and scaleable’ a little bit too much at face value).
Use J.D for files in files. (two digits)
Use J.D for notes in notes. (with three digits)
And overall, treat those three ‘spheres’ as intermingled, but, ultimately separate (notes, tasks, files.)