Get the full video course with 9h 45m of content as well as the downloadable PDF and ePub at: www.atomicworkflows.com/atomi... --- Blog: meda.io Twitter: / martin_adams
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.
![โกหกเธอทั้งนั้น (Pinocchio) - SERIOUS BACON [Official MV]](http://i.ytimg.com/vi/P1HhTYwrR5A/mqdefault.jpg)
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.