How I'm using the Slipnote method to build better notes in Logseq

Поділитися
Вставка
  • Опубліковано 27 лип 2024

КОМЕНТАРІ • 38

  • @TonySilveiracanada
    @TonySilveiracanada 2 місяці тому

    Excellent, this helped me create a hierarchy for my notes

  • @MaxwellBuba
    @MaxwellBuba 17 днів тому

    Very good video. I only write in bullet points. Create a hierarchy. And because of this hierarchy collect them under headlines and the note becomes atomic.
    MOC (map of content) leads to other MOCs and then you are in the train of thoughts.
    I use the app Obsidian. Linking thinking

  • @GOZES
    @GOZES Рік тому +6

    It would be really useful if you could expand on this video by showing the whole process from capturing to output in logseq :)

    • @toolsontech
      @toolsontech  Рік тому +2

      I'm planning to write down an extended flowchart of all my inputs and outputs since I want to clean it out and once I have that I'll probably do a quick going over it video first and a refined video later.
      Good plan!

  • @MrMartiiine
    @MrMartiiine Рік тому +1

    Thank you for the rpocess ! I'm sure your video notes will fit great in that structure with the Whiteboard

  • @toranshaw4029
    @toranshaw4029 Рік тому +1

    I really am going to have to start using the block embed feature, so ta for the reminder. 🙂

  • @gedankenbalance
    @gedankenbalance Рік тому +2

    Great Video. Thanks! You pointed out really good the advantages of embedding the Blocks instead of moving them to a new place. I will definitly give it a try.

    • @toolsontech
      @toolsontech  Рік тому +3

      Glad that it gave some good ideas, I will return on this video in 6 months or so to talk avbout the long term lessons and refinements. Mostly around larger and larger notes I expect. :D

  • @kazerniel
    @kazerniel 4 місяці тому

    thanks, this method helped me a lot!

  • @alxlg
    @alxlg Рік тому +6

    Notes and tasks as opposites was enlightening.
    I see you also use hashtags at the end of blocks. I changed the CSS to align those tags to the right and it looks much neater and more pleasing to the eye.
    It is true that compiling indexes and moving blocks around is a great way to review your notes.
    Some say they use a PKM so they can forget things. On the contrary, I use it to fix them in memory and structure is an important part for memorization.

    • @toolsontech
      @toolsontech  Рік тому +2

      Good idea, added "a.tag { float: right; }" to my custom.css to give it a go.
      True, while I do forget a lot of notes, having to skim them and re-order them has a similar effect to flashcards I think. But I'm kept busy while doing so. And the good notes stick around.

    • @rrarrtutorials
      @rrarrtutorials Рік тому +3

      OMG, this is a cool way to quick scan of journal page, tags can be used like a category label in the journal page.
      Thanks for the idea!

    • @kenfhill84083
      @kenfhill84083 3 місяці тому

      @@toolsontech thanks for the CSS tip. tags look much nicer

  • @pierrecuomo9207
    @pierrecuomo9207 4 місяці тому

    So interesting, thanks a lot.

  • @tomdavey1887
    @tomdavey1887 Рік тому

    Wonderful video. This video showed me how Logseq could help solve my number one concern which is re-writing the same insights and stuff over and over every few months. This feels like a possible simple, concise, and ITERATIVE note taking approach. Embedded blocks is a huge step forward.

    • @tomdavey1887
      @tomdavey1887 Рік тому

      Compound Interest = Iterative Notes

    • @toolsontech
      @toolsontech  Рік тому

      Exactly, while it still requires work it improves the notes over time. I love this method just wish I had more time to dive deep on topics.

    • @Rhantismos23
      @Rhantismos23 Рік тому

      @@toolsontech How do you get the two bullets to stay like that? when i block embed the two bullets don't stay

  • @matrhein
    @matrhein Рік тому

    Bas, that one was really a great primer for developing my own system, thank you so much for this! The readwise embed warning sadly got lost in the final content and was only briefly visible in the video- but it piqued my interest, since I am depending on Readwise quite a lot these days. What is the problem with Readwise in the process? Looking forward to your videos, keep up the good stuff you're doing right now!

    • @toolsontech
      @toolsontech  Рік тому +1

      The readwise warning was about the fact that at the time of making this it had conflicts with sync, currently going through a couple of audio books so haven't checked if the issue is still there with the latest sync update. In general it means that the readwise produced page syncs late and requires a reindex if that's the case.

  • @orusmateo
    @orusmateo Рік тому +1

    Thank you for this!
    Question: have you found a comfortable way to use Logseq PDF annotation on a tablet?

  • @1monki
    @1monki 10 місяців тому

    I use a 10-directory/node method of high-level organization. The highest level is 100-900. The numbers ending in 0 are collection nodes. They hold related hierarchies. So, 300_Computer -> 310_Python -> 311_Strings. Everything 31X is related to Python. Everything 311 are notes related to strings in Python. The numbering system forces a limit on the number of organization nodes. The zero numbers must be general enough to capture related interests but specific enough so you'll know where to find the area to search or store information.

    • @toolsontech
      @toolsontech  10 місяців тому +1

      Interesting, so each level has a 10 element limit. But can you for example switch out topics? Say you start hating Computers, could you replace 300 with "Clay Tablets"?

    • @1monki
      @1monki 9 місяців тому

      @@toolsontech Sure, I guess, but that's not usually the case. Usually, a category changes from more focused to less focused. So a category might change from "Spanish" to "Foreign_Languages." Spanish is still in there, but it's a sub-category listed with other languages.
      And I can create as I go. So I can start with 300_Computers and connect everything to that. When I collect enough for groups to form, I can create sub-categories to organize them more. This is for long-term storage. Temp projects are their own thing.

  • @vitruvianmask
    @vitruvianmask Рік тому

    hmm interesting concept. TIL 🤷‍♂️
    btw, new studio right, Sensei? looks awesome 👍

    • @toolsontech
      @toolsontech  Рік тому +1

      Thanks, it was a bit of work but together with less noise and a better recording workflow I hope to get more content out without dropping too much quality.

  • @TheJeanmariusnilura
    @TheJeanmariusnilura Рік тому

    Hi! A really really better take on Zettelkasten than your book is probably videos by Bob Doto

    • @toolsontech
      @toolsontech  Рік тому +1

      I thought slipnotes where different from Zettelkasten, was planning on diving into it a bit more so will check out Bob Doto and some books on the topic before I make a followup.

  • @kenfhill84083
    @kenfhill84083 3 місяці тому

    In my linked references sections, the linked items keep shifting positions. It is so annoying it makes linked references almost unusable. In your video they stay put. Is there a setting I need to change? Thanks. Your videos are very clear and useful.

    • @toolsontech
      @toolsontech  2 місяці тому

      Linked references are sorted on journal timestamp and then pages. Really shouldn't be moving around. I would debug it by making a new test graph and seeing if it happens there as well. That will at least tell you if it's global or graph related. After that hit me up and I'll help you think to resolve it.

  • @Scoop9599
    @Scoop9599 11 місяців тому

    Quick technical note:
    The video looks weird, like your shutter speed may be set too long or something. You look kinda jittery and oddly blurry at the same time. Actually, I think it may be your encoding.
    But great information, thanks for the video.

    • @toolsontech
      @toolsontech  11 місяців тому

      I'll have a quick rewatch when I'm at my editing station.

  • @nabbopersempre7004
    @nabbopersempre7004 Рік тому

    Why I like your videos but often I can't understand almost anything? perhaps Logseq it's too difficult for my brain

    • @toolsontech
      @toolsontech  Рік тому +1

      Finding what works for your brain is an important part, feel free to ping me in the DMs if you got questions or just want some feedback. hearing what is unclear helps me a lot.

  • @JamesBond-xv1ly
    @JamesBond-xv1ly Місяць тому +1

    I watched this video from start to finish, and have no idea what this guy is talking about. Why are videos about note taking so frustrating all the time? Is there videos about notetaking apps for normal human beings? They are really hard to find, to tell you the truth.

    • @toolsontech
      @toolsontech  Місяць тому

      That's too bad, I try and make things simple but this one in particular is really getting into using the more advanced features of Logseq. No matter how I cut it, a video is always aimed at a general audience so if you still didn't find anything hit me up on DM and we can always have a call. No costs, I really like talking note taking and love seeing how other people struggle or tackle the issue so I can help out.

    • @DmitryRomanov
      @DmitryRomanov Місяць тому

      Video is fine (imho)

    • @DmitryRomanov
      @DmitryRomanov Місяць тому +1

      1. The way you use the note-taking for depends on your goal.
      - In the beginning no one has a clear goal, so just grab something and start to write and copy/paste any stuff you think you need to remember.
      - I recommend something Markdown based (it forces you into a simpler style) and local folder based.
      - DO NOT create preliminary folders/tags/... structures! It will never work and never did, you will just waste time.
      2. Once you have many notes, you will have a troubles finding the stuff you need. Start linking things together and regroup them together.
      - DO NOT classify, unless you are a librarian - let it grow organically, and the structure will emerge. Grow organically means, for example, looking somewhere, finding it in another place, and moving the stuff you found into the place you started to look for it in the first place (or dropping a link there).
      - make a decision, what do you use your system for: to support knowledge collection/thinking, or to support your workflow
      - knowledge stuff and writing:
      - read Sonke Ahrens book, Cal Newport book (Deep work)
      - workflow
      - read Getting Things Done by David Allen
      3. At that point you will have a set of troubles we all have, and this video will make sense)))
      P.S. Difference between knowledge garden and workflow is that the result of the first one is a deep structured book describing something you really want to know. In the second case, you will have a set of clearly defined actions that will be easily applicable in any context where they are needed.
      P.P.S. There are hybrid systems like PARA by Tiago Forte, but the basis is to start from 1. and work your way without making stuff complicated unless you need to. Just start writing and go forward. Good luck to you!