Your video made it in my zettelkasten 😂 loved that idea for creating mini quests. Im brand new and following a slightly modified zettelkasten from a different youtuber that uses daily notes as well and "hubs" as sort of a subject specific collection of permanent notes. I like the idea of setting up a hub and adding to it my mini quests as if it were an index of lessons in a book that i will later go and write myself.
Hey Martin! Thanks for sharing your flows. If you have a moment then I would like to ask you this though - when learning something completely novel this form you present makes sense. What about practical projects, when doing product development, writing grants or building a company one doesn't have time to sit and synthesize every concept and thought, nor double back with every thing that they have learned to add references and links and separate into comprehensive notes. When I'm writing a grant I'll go through hundreds of documents, word of mouth, own expertise, combine the ideas and polish it so it looks just like the evaluator wants - and I'll have 2-3 days to do this, not months. How do I deal with the information if there is so much of it in such a short time, with no time to slow down? How do I pick and choose the bits that I will actually have time to write down to be those that I will actually have use for later on, compared the vast majority of it which will never come up again, will become irrelevant due to time, or becomes so obvious to me it doesn't need writing down?
Thank you Timmy for such an insightful question. Rather than answer it here, I made a video instead which I hope helps: ruclips.net/video/OFyF-ygduF4/видео.html
Would you say that taking Atomic notes work better than Fleeting notes in creating Zettlekasten for technical learning? I've watch your video of atomic notes and fleeting notes but do not seem to understand where these two techniques can fit into the flow of taking note. Is that Atomic notes just the break down of fleeting note after the lecture? Thank you.
Great question. In a technical context, I would say that fleeting notes is the capture of what steps you take, or rough notes on a topic. For example, installing an Apache web server, you might capture things as you’re doing it, but at some point you might discover some of those steps weren’t required. Literature notes (atomic nature of those steps) are your refined and more concise steps. Permanent notes is when you start to bring it into the wider ecosystem, such as adding a database, proxy server, adding secure certificates. The atomic nature of those notes is that you could link to individual steps where necessary. For example, forwarding your request to a PHP application could point to just the atomic step where you set up the routes in Apache. You add an intermediary note which says how to modify that file in Apache. Then it’s easy to swap that for Nginx for example. I hope that makes sense. Great question and I’ve been thinking about what would be some great videos to make specifically on creating technical notes.
@@Martin_Adams Thank you for the detailed explanation. I might not get it fully at first, but I'll take the time to practice and see how does it fit into my system. Love your content.
Your video made it in my zettelkasten 😂 loved that idea for creating mini quests.
Im brand new and following a slightly modified zettelkasten from a different youtuber that uses daily notes as well and "hubs" as sort of a subject specific collection of permanent notes. I like the idea of setting up a hub and adding to it my mini quests as if it were an index of lessons in a book that i will later go and write myself.
Hey Martin! Thanks for sharing your flows. If you have a moment then I would like to ask you this though - when learning something completely novel this form you present makes sense. What about practical projects, when doing product development, writing grants or building a company one doesn't have time to sit and synthesize every concept and thought, nor double back with every thing that they have learned to add references and links and separate into comprehensive notes.
When I'm writing a grant I'll go through hundreds of documents, word of mouth, own expertise, combine the ideas and polish it so it looks just like the evaluator wants - and I'll have 2-3 days to do this, not months. How do I deal with the information if there is so much of it in such a short time, with no time to slow down? How do I pick and choose the bits that I will actually have time to write down to be those that I will actually have use for later on, compared the vast majority of it which will never come up again, will become irrelevant due to time, or becomes so obvious to me it doesn't need writing down?
Thank you Timmy for such an insightful question. Rather than answer it here, I made a video instead which I hope helps:
ruclips.net/video/OFyF-ygduF4/видео.html
Great work! Thanks a lot for the video.
I'm building my Zettlekasten of technical notes too.
Would you say that taking Atomic notes work better than Fleeting notes in creating Zettlekasten for technical learning? I've watch your video of atomic notes and fleeting notes but do not seem to understand where these two techniques can fit into the flow of taking note. Is that Atomic notes just the break down of fleeting note after the lecture? Thank you.
Great question. In a technical context, I would say that fleeting notes is the capture of what steps you take, or rough notes on a topic.
For example, installing an Apache web server, you might capture things as you’re doing it, but at some point you might discover some of those steps weren’t required.
Literature notes (atomic nature of those steps) are your refined and more concise steps.
Permanent notes is when you start to bring it into the wider ecosystem, such as adding a database, proxy server, adding secure certificates.
The atomic nature of those notes is that you could link to individual steps where necessary. For example, forwarding your request to a PHP application could point to just the atomic step where you set up the routes in Apache. You add an intermediary note which says how to modify that file in Apache. Then it’s easy to swap that for Nginx for example.
I hope that makes sense. Great question and I’ve been thinking about what would be some great videos to make specifically on creating technical notes.
@@Martin_Adams Thank you for the detailed explanation. I might not get it fully at first, but I'll take the time to practice and see how does it fit into my system. Love your content.
Did you adjust the nodes of your graph view to look like a doughnut, or is that purely coincidental?
Haha, nope. The universe is telling us something 😆
@@Martin_Adams Excellent!