Hey everyone,
I’m still getting used to the Johnny.Decimal system and liking it so far, but I’ve hit a bit of a snag. What do you do when a project could realistically belong in two different categories? For example, a client job that also involves internal training material.
Do you just pick one and stick with it, or is there a clean way to cross-reference?
Thanks!
Hi, welcome to the forum. 
I try to stick with one place but are not hesitant to copy results and artefacts that might be useful elsewhere to another matching place. However I only do this if it is clear that these won’t change further because keeping things in sync is a pain.
Kind regards,
If the client project contains some other stuff from your system – the internal training material – you have a few options.
If the training material is static, it’s okay just to copy it inside the project. And I suppose even if the training material then gets updated, the version delivered to the client probably doesn’t, so now you have two diverging sets of data but that reflects the actual state of the world.
If you don’t want to do this, this is what your JDex is for. In the client job note, you can just reference across to the training material. This is why I recommend apps like Obsidian or Bear: they’ll automatically show ‘backlinks’ between documents.
So in Obsidian:
I always keep short notes and metadata above a line, then my daily scribbles below the line.
And now, automatically, over in 11.51, after you check Backlinks in document to turn it on…
The real trick here is remembering that these links exist. Backlinks are super powerful when you look at them!
Create them liberally and use them often.
I have a blog post in draft for this, but the heuristic is to link ‘up’ from the thing that might get duplicated, to the thing that’s more static.
You’re way more likely to create another job than you are to create another ID for internal training material. So link that way. Because it can be convenient to duplicate note in your software when you create that new job, and then your links come along for the ride.
