Great video! From looking back over your channel I think we have a similar way of working and thinking. I have found myself flitting between Obsidian and Logseq, both seemingly giving their own benefits, but neither being quite right for me to use them exclusively. This gave me great insight into how the tools work well together. Glad I found your content and looking forward to seeing more!
Hey Jamees, thanks for the comment! Really glad you found the video useful and that I'm not alone in the hybrid approach to knowledge management. Best of luck as you continue to build out your systems. :) Have a wonderful day.
This video is really great. I feel it will help me to solve the mess I currently have about my notes spread everywhere. I loved outlining with Logseq and love Obsidian for PKM. Not only that, but I was constantly switching between those apps and not having a well organize process about it. And if I look at my Obsidian I feel like I have interesting notes lost in a bunch of useless note which was quick capture. With this video, you gave me a great example on where to put the line and how to get the best of a book. Thanks for sharing.
That would be great to see how you skim. I'm trying to adjust my habit of reading books front to back which doesn't work very well if I have a limited amount of time to read them. I generally retain a lot from my slow reading process, but in order to get the gist, I'm still working on that style. How to Read a Book by Mortimer J. Adler first taught me this, but now that I have the Smart Notes concept, with help from you and others, hopefully I can work on a system that works well under pressure. Thanks and keep it up man!
Hey Aaron, This is a very useful comment. I'll give it some thought and figure out how I can share my learnings from combining the four levels of reading with smart notes. One nugget I'll share is I only take notes on books that I've decided to read analytically. Which is about 40% of the books I pick up. For the others I at most mark them up for future reference, but never take the time to extract them into smart notes. Thanks for the comment!
@@joshuaduffney Ah, yes! This concept is talked about too in How to Read a Book. Mortimer says that only a few books are worth reading analytically. And I tend to approach each and every book that way. That's why I've been amazed at these other RUclipsrs who say they read all these books. How can you read so many I would ask myself. But that makes sense if they're not digesting each and every thought. I'll keep that in mind. Thanks for the tip!
Great video, I'm trying to do something similar. My idea is to implement a customized para method in which the folder Resources is the root for loqseq. So in that folder, everything is flat level. Then my refined notes will go in Areas, which is divided in folders.
That's a great idea! I have a feeling my methods will change after I read "Build a Second Brain" looks to me like you're well on your way to adopting those ideas and making them your own.
Impressive work :) but I'm not convinced. No offense, if you like it, keep doing it. My impression is, that you invested too much time in collecting notes on stuff you can just google when you need it. I think the topic doesn't warrant this kind of analysis. Just read how it works and start using it. I would also caution you against falling into the trap of self-help books, like Ryan Holiday. These guys know how to blow up the tiniest inconsequential topics, to make them sounds smart and important. These are pure sales people, like Tony Robbins. They have no formal academic background, and pretty much talk out of their ass. Except for Adler, but his book was (a) written before the digital age and (b) meant to be used on complex knowledge, like philosophy or sciences.
Humm, great insight and thank you for your comment. I agree, there's still too much friction in the system. Having gone through several iterations of knowledge management I can safely say that for me the benefit has mostly come from the effort invested in taking the notes. It's slowed me down enough to fully digest and understand the information I'm consuming. But, the last step where you re-organize the knowledge has an imbalance of effort and reward. Perhaps that level of effort should be reserved for creating a new artifact of knowledge like an article, essay, or manuscript. That said I still think there is an opportunity to turn the notes taken as I learn into something useful. Your comment has given me some food for thought, thank you for taking the time to write it. :)
@@smonkdivines great point, the bet part of sharing what you're doing is getting valuable feedback like this that makes you re-think your workflow. Thanks for the comment! :)
I have to agree on self-help traps and most of the authors being good sales people. I disagree, however, on your advice to just google information. Taking notes and "digesting" the information, lile josh said, is far more valuable than just searching and finding the answers. Of course the information is out there somewhere on the internet, but if you integrate it into your own mind, you can play with it, put it in different contexts. You may even unconsciously combine information. In addition your own knowledge collection has a unique perspective, a unique flavor if you will and that adds tremendous value. If everyone just googles information, than all optinions are based on the same sources they will find.
@@tobiasr5073 Taking notes can be useful or needed, like in a testing situation, where you are questioned on the details. But as far as I understood the author, he just wants to learn some programming. That's why I think it's a waste. If you take notes on everything you read somewhere/ want to remember, you'll never get anywhere. Have to pick your battles. Also, there are no more than one opinion on the programming language's syntax, because it's a fact.
Great video! From looking back over your channel I think we have a similar way of working and thinking. I have found myself flitting between Obsidian and Logseq, both seemingly giving their own benefits, but neither being quite right for me to use them exclusively. This gave me great insight into how the tools work well together. Glad I found your content and looking forward to seeing more!
Hey Jamees, thanks for the comment! Really glad you found the video useful and that I'm not alone in the hybrid approach to knowledge management. Best of luck as you continue to build out your systems. :) Have a wonderful day.
This video is really great. I feel it will help me to solve the mess I currently have about my notes spread everywhere. I loved outlining with Logseq and love Obsidian for PKM. Not only that, but I was constantly switching between those apps and not having a well organize process about it. And if I look at my Obsidian I feel like I have interesting notes lost in a bunch of useless note which was quick capture.
With this video, you gave me a great example on where to put the line and how to get the best of a book. Thanks for sharing.
Great video! Thank you for covering this topic on Logseq!
You're very welcome, thanks for watching. :)
Thanks for the video Josh, really great stuff! I have a whole bunch of fleeting notes that I have to organize and simplify and this is a great method!
Glad it was helpful! Best of luck with the fleeting notes. Just keep in mind the vast majority should be forgotten. :)
فيديو رائع، جزاك الله خيراً علي هذا الشرح الممتع
That would be great to see how you skim. I'm trying to adjust my habit of reading books front to back which doesn't work very well if I have a limited amount of time to read them. I generally retain a lot from my slow reading process, but in order to get the gist, I'm still working on that style. How to Read a Book by Mortimer J. Adler first taught me this, but now that I have the Smart Notes concept, with help from you and others, hopefully I can work on a system that works well under pressure. Thanks and keep it up man!
Hey Aaron,
This is a very useful comment. I'll give it some thought and figure out how I can share my learnings from combining the four levels of reading with smart notes. One nugget I'll share is I only take notes on books that I've decided to read analytically. Which is about 40% of the books I pick up. For the others I at most mark them up for future reference, but never take the time to extract them into smart notes.
Thanks for the comment!
@@joshuaduffney Ah, yes! This concept is talked about too in How to Read a Book. Mortimer says that only a few books are worth reading analytically. And I tend to approach each and every book that way. That's why I've been amazed at these other RUclipsrs who say they read all these books. How can you read so many I would ask myself. But that makes sense if they're not digesting each and every thought. I'll keep that in mind. Thanks for the tip!
Great video, I'm trying to do something similar. My idea is to implement a customized para method in which the folder Resources is the root for loqseq. So in that folder, everything is flat level. Then my refined notes will go in Areas, which is divided in folders.
That's a great idea! I have a feeling my methods will change after I read "Build a Second Brain" looks to me like you're well on your way to adopting those ideas and making them your own.
thats a nice template for logseq that im totally jacking
Could you please share your template for your daily note?
So sorry for the delay! Here's a link. :)
gist.github.com/Duffney/ec3cff8245771d77aecfb657408d50fa
@@joshuaduffneythank you I’m revisiting this video coming back to logseq and this was right on time! ❤
Impressive work :) but I'm not convinced. No offense, if you like it, keep doing it. My impression is, that you invested too much time in collecting notes on stuff you can just google when you need it. I think the topic doesn't warrant this kind of analysis. Just read how it works and start using it. I would also caution you against falling into the trap of self-help books, like Ryan Holiday. These guys know how to blow up the tiniest inconsequential topics, to make them sounds smart and important. These are pure sales people, like Tony Robbins. They have no formal academic background, and pretty much talk out of their ass. Except for Adler, but his book was (a) written before the digital age and (b) meant to be used on complex knowledge, like philosophy or sciences.
Humm, great insight and thank you for your comment. I agree, there's still too much friction in the system. Having gone through several iterations of knowledge management I can safely say that for me the benefit has mostly come from the effort invested in taking the notes. It's slowed me down enough to fully digest and understand the information I'm consuming. But, the last step where you re-organize the knowledge has an imbalance of effort and reward. Perhaps that level of effort should be reserved for creating a new artifact of knowledge like an article, essay, or manuscript. That said I still think there is an opportunity to turn the notes taken as I learn into something useful. Your comment has given me some food for thought, thank you for taking the time to write it. :)
Yeah, I see the good part is in Logseq
Put in obsidian isnt necessary
@@smonkdivines great point, the bet part of sharing what you're doing is getting valuable feedback like this that makes you re-think your workflow. Thanks for the comment! :)
I have to agree on self-help traps and most of the authors being good sales people. I disagree, however, on your advice to just google information. Taking notes and "digesting" the information, lile josh said, is far more valuable than just searching and finding the answers. Of course the information is out there somewhere on the internet, but if you integrate it into your own mind, you can play with it, put it in different contexts. You may even unconsciously combine information. In addition your own knowledge collection has a unique perspective, a unique flavor if you will and that adds tremendous value. If everyone just googles information, than all optinions are based on the same sources they will find.
@@tobiasr5073 Taking notes can be useful or needed, like in a testing situation, where you are questioned on the details. But as far as I understood the author, he just wants to learn some programming. That's why I think it's a waste. If you take notes on everything you read somewhere/ want to remember, you'll never get anywhere. Have to pick your battles. Also, there are no more than one opinion on the programming language's syntax, because it's a fact.