(hidden) g2IT-5G5b | notes | kipras melnikovas

Linked Mentions (2 in 1 page)

thread (2)
- and this (specifically, (2)) is when i realized that something like a [[thread]] or [[(hidden) g2IT-5G5b]] would work well.
- testing. maybe #[[(hidden) g2IT-5G5b]] would work as well
  - #[[(hidden) jOMmlCP4S]] comes from:
    - the #[[(hidden) L_G_h4Jr_]] is that if you write new paragraphs, but related to the previous one, you tend to indent them, and the indentation continues so much, when it really shouldn't. the #[[(hidden) jOMmlCP4S]] i had for [[(hidden) -NklLsZCV]] when doing [[export-html-pages]] is that when you have a block that has children, but only 1, you can safely undo the indentation, as long as 1. the first (top-to-bottom) child that is not the only 1 child, is not being un-indented, and 2. to separate it out from the other children which are not related as much because you didn't originally indent them, you'd have to indent the 1 child.
      - and this (specifically, (2)) is when i realized that something like a [[thread]] or [[(hidden) g2IT-5G5b]] would work well.
    - the other problem is that if you do a block reference, and it's the non-normalized way, you can easily find the related blocks by just looking at the referenced block's children. but when it's normalized, then that's no longer the case, and especially with [[roam]], you have to do extra work to see the stuff.
      - but, now what i realize is that you can reference the [[thread]], and as long as you're giving a good description for the thread (when you start it, at the same block), it might even be a better way to both find things, and to have a more precise count of how many times you've referenced the thread, instead of it's specific children
        
        {{[[TODO]]}} oh wait you're kinda losing precision if you're referencing the thread instead of one of it's children
        
        what would be the preferred way, is to reference the exact thing that you want to reference, and then enhance the blocks with the [[thread]] tag / attribute to show the total count of references of it's children - win win, because both precision and total count
        
        re:: enhance -- could create a [[roam/js]] extension for it
        
        {{[[TODO]]}} scope, global variables, and normalization turning everything into the same level, making it more complex because you have to keep track of all of the previous things, instead of knowing what the current point relates to
        
        fuck this whole notion of what's better & worse is complicated. you can see it right here, on the meta level.

words:	0 + 402 = 402
last update: