Document what you do, as if you were describing your work and/or learning to a stranger. That stranger is you, in 6 months to 5 years time.
Maintaining that enthusiasm and finding the time to document is difficult, but the results are very valuable because you are building a "second brain". That extra brain can be indexed, searched, tagged, analyzed, and edited using many powerful tools.
Don't waste energy chasing fancy tools and methodologies without already having a simple workflow in place. In other words, don't go all out learning Emacs+org-mode+org-roam when you already have a directory of text file notes. Once you have a good idea of what works for you, then introduce tools designed to make your life easier. (I say this as someone who uses Emacs+org-mode+org-roam every day)
Oh and read "The Checklist Manifesto" and "How to take Smart Notes".
I have read over 100 pages of the book but to be honest, I am disappointed with it. I learn best by examples, the book is failing short of examples on how to use Zettelkasten. My expectation was the book was going to walk me through the process of implementing Zettelkasten like a tutorial, but instead it keeps going back in circles, talking about why I should use Zettelkasten. I am about to finish the book but I still have a lot of questions.
Yeah, that book was pretty light on practical advice. I didn't find much in there that I hadn't already discovered by reading blog posts about it
One thing that was unique though, was a set of questions to ask yourself while reading to get extract the most insights out of the material.
I posted them here if you're interested:
Why bother? Sometimes they help to convey emotion that would otherwise be missing. Other times it helps to break up dryer blocks of text.
That, plus it's fun :)
My second reading of Test Driven Development, I literally did the entire book along with the author, front to back.
That's when it clicked. The actual manual mechanical kinesthetic activity somehow made it work for me.
Seemingly, one of those lessons that must be experienced to be learned.
30 years ago, I added full comments to (my source of) a text editor during a rewrite. Back when we still debated such things, before Code Complete 1st ed.
Thereafter, all maintenance was a breeze, even years later. Like a gift from my prior self.
When I write (code, notes, journals), my headspace is kind of a hybrid of rubber ducking (thinking out loud, like during usability testing) and telling future me a story of me.
100% agreed on the "don't chase fancy tools" mindset.
When I was taking the Building a Second Brain course, the instructor Tiago Forte had offered us three tools to use for organizing our notes:
He personally used Evernote, but he had an interview each with someone to show us how hey used Roam or Notion.
Since all the examples he would show us during the class would be in Evernote, I decided to not bother trying to apply PARA to the other two systems and stick with Evernote until I learned the basics. I could always switch over later, once I grasped the fundamentals better.
I haven't switched over yet, because frankly, Evernote is still good enough for me. The potential switching costs aren't worth it.
I picture it as "doing engineering the way a coroner conducts an autopsy." (Maybe only a helpful framing if you've watched enough CSI, but IMHO a pretty powerful mental lever if you have.)
How we implement it:
1- he and I annotate almost everything we read worth annotating (I wont do it for escape reading)
2- our annotations have similar systems across books. Underlines may be something fun or interesting, stars highlight significant points, “Qs” pose thoughtful questions, top left corner is location in plot top right is general theme of the scene etc
One and two allow us to get up to speed on a book we previously read very quickly or find particular sections in an instant.
For teachable items - books or notes I don’t want to forget that are nuanced - I transcribe my annotations to OneNote (my favorite note taking app).
For example I read a book about Japanese death poems. There were a few that really resonated to me. I don’t need to ever pick this book up again nor do I need to remember any of them, I just have to remember I wrote them down. Here is one of my favorites:
is a bottomless river,
a raging torrent.
(Written by a woman who took her husbands life, for taking the life of her brother, moments before she took her own.
Anyway this system works for me and thought I would share.
I also really like writing notes in the book, but I take a picture of each page and stick it into Evernote. On each note I'll write down the book and page number that the note came from in case I want to see it in more context.
That way the notes are all searchable and it really helps when I don't remember which book I read something in
Not affiliated, just a fan!
either way, underrated open source, free, note taking app.
Actually, I can just be that guy as I use it myself, and it is great. However I do find myself spending energy I wish I didn’t on meta-things like how to organize it all (files, tags, hierarchy etc). I think it could benefit from having preconfigured setups like doom-emacs or ruby on rails or whatever («convention over configuration»). One for a hardcore GTD, one for zettelkasten, one that is bare bones, etc..
I realize the agenda should make this less important, but I still get caught up in it from time to time (tags? Properties?)..
I haven’t tried org-roam though. I just feel like theres so many moving parts to my setup already. Anyone had any good/bad experiences integrating it into your workflow?
Speaking of org-mode, maybe I should start looking at those scheduled items in my agenda that are now some 600 days+ past its due date...
I _still_ haven't figured out how to use org-agenda properly, and it feels like I'm missing a lot of core functionality as a result.
I tried to get into org-brain for a while. It never stuck for me.
RoamResearch was a lot stickier; I may end up back in it at some point because of the mindshare and effort being poured into it. It's a really great product--my threshold for being willing to do my thinking work inside a program that's finely tuned to distract me (the browser) is high, so this is saying something.
In the meantime, though, I've been giving org-roam some love, more than anything else because it's _not_ in the browser distraction machine (to wit, here I am commenting on HN when I should be billing time...). Getting spun up and fully in the habit of using org-roam took me a couple days of background effort. I find it easy enough to forget it's there, which is good enough for me.
I wrote this article last May and back then it was unclear whether or not I'd stick with PARA
Here's the update three months later:
The Bad: I’m kinda getting falling behind on some of the proactive archiving/organizing parts of it, especially for my personal notes
The Good: Falling behind where PARA's Just In Time aspects really shine. I can organize just the notes that I’m about to use
The Great: BASB made a night and day difference to my project management style
In the past I organized my notes and todos in a completely different way. I was constantly struggling to find the important bits or would miss important tasks. I'd always be feeling overwhelmed and lost
I still feel like that today, but it's no longer because of my notes. My system is no where near perfect now, but it's waaaaaaay better than what it used to be
I shared more of my thoughts in this tweet thread  describing the advice I've been giving to my friends who asked if they should sign up for the Building a Second Brain class (where I learned PARA)
Personally, I've come to the conclusion that I read in order to draw broad patterns, not necessarily to remember all the things in every book - my brain has limited space.
What are your thoughts on optimizing retention at the expense of remembering to see the forest?
Now I try to only save notes that I found particularly surprising or insightful, I'm definitely not trying to save everything in the book. I don't put it in:
* If the fact didn't make me think
* If it doesn't trigger an "aha" moment
* If it was something I already knew,
For example, I'm currently taking notes as I read The Art of Doing Science and Engineering. If you looked at my notes then you could barely tell that it's a book about engineering.
Almost all of what I read is not on paper. If I'm reading something that I'm serious about remembering, I'll create a precis ("a concise summary of essential points, statements, or facts" ). My goal is to reduce the size of the content by 90% or more (10 page article becomes a 1 page precis, 200 page book becomes 20 page (or smaller) precis. The process of creating the precis seems to enhance my recall of the important information, and if I need to refresh my memory of the material, I can do it in a tenth of the time.
That way I can quickly catch a glimpse of what the note offers as soon as I open it, and in case I need to understand the arguments behind those points, all I have to do is to scroll down.
This has proven to be quite effective when I want to reference something I've read about years prior.
I tried doing that and failed miserably however, I just couldn't stick with it, lol. That's where PARA's highlight based, minimal effort note taking system really helped me out.
Is it the best option for everyone? Definitely not. But the system that I can stick with beats one that I won't follow.
Graphs with labeled edges seem clearly better. But then what if you want a relationship with more than two members? (Or less! "Not" and "maybe" are two important unary relationships.)
Once you've reified your relationships that way, you'd like to be able to search intelligently through them. "Ordinary" knowledge graphs let you see all of a thing's children, or parents, or maybe in some cases all it's descendents and ancestors up to some level of recursion. Better would be something that lets you ask targeted questions, like "Show me everything Sally has asked me to do that does not require a computer."
To my knowledge there's only one program that lets you reify your data and query it in the ways I've described. It's called Hode, for Higher Order Data Editor. I wrote it.
How much work does it take you to add your notes to it? I'm curious about it on two dimensions:
* The time it takes to add a note
* What decisions you need to make to add a note (what to link it to, what not to)
You've zeroed in on the weakest point of the program. Adding notes is mechanically easy but conceptually hard. That's because there are many ways you could choose to represent the same concept.
For instance, suppose "harry gave sally a book" is in your graph. One way you could represent that is "Harry #gave Sally #object a book". Another is "Harry #did (give #object a book) #to Sally". Another is "Harry #did (give #object a book #to Sally)". And actually maybe you'd prefer to represent "a book" as "#a book", so that you can just search for "book".
They're all plausible representations, and all have different implications for how you would run searches. You've got to be consistent in how you represent those relationships, and the program can't help you because I mean it's a database, not a general artificial intelligence.
The strength of the program is that the structure of your index is entirely up to you. But soon that freedom gives way to being bound by the decisions of your former self. And your future self will inevitably understand the space you're representing better than your former self did when it bound you.
Just a thought: if I were interested in adopting a tool like that, my chances of successfully sticking with it would go up 100x if there was a set of "default recommended practices" to follow when saving a new note, to cut down on the decision I would need to make.
Then over time, as I got more familiar with the tool, I could always tweak those default recommendations to fit into my own style
And who better to offer those default practices than the tool's creator? :)
I would pay money for a service that was able to grab these highlights and put them into a Zettlekasten or P.A.R.A. style repository. Even Toi Lutke made something to help accomplish this... https://github.com/tobi/highlights
Instead of complex note systems, try this: write down quotes, paragraphs, summaries and other related information, add them to Anki / another SRS, and do the cards everyday. That’s it. Simplicity is key to building habits and I’d bet any money that SRS works better anyway.
Spaced repetition is super valuable when you want to keep all the information inside your head. PARA is more geared at when you want all the information available when you need it, and requires much less time/effort than Anki (I've tried both).
Not to say that one is better than the other. Sometimes you need to access the information and cannot use the note taking system (e.g. you're a student and have a final exam coming up). But if memorization is not a requirement, then I find these other systems easier to use.
When I began to apply a structured method to my studies, my first choice was to use mind maps. You can structure a mind map to resemble the associations you have in your own (duh) mental model of any body of knowledge you might be studying, and then it's easy to navigate a map with your eyes to recall stuff and fill the gaps when things get cloudy in your head. The first digital tool I recall using was CmapTools, and it's still pretty good.
Nowadays I use mostly LiquidText for reading notes, on books and articles (but there are other similar products). It lets you build something similar to a mind map, and it's really convenient to select a piece of text or image on a pdf and make it a node in a map. It's especially convenient if you have an iPad Pro with a Pencil. However, I could still not find any single tool that encompasses all my "learning modes". For instance, if I am playing with some OSS project and want to take note on something interesting, I have to use a different product.
That said, it's dangerous to let the perfect be the enemy of the good. I'm trying not to spend too much time researching new systems and instead focus on benefiting from the good-enough system I currently have. I moved to my current system when I was feeling the scaling pains of my old one, and when I feel those pains from this system it'll be time to search for an upgrade!
Speaking of upgrades, I don't have a good way to take notes from pdfs. Looking at their site, LiquidText seems like it's optimized for the pdf use case. I'm going to dig deeper into it to see if I can read pdfs and take notes in there, and then export those notes into Evernote. Thanks for the tip!
Emvi  has a tag overview page to allow just that, in case you're interested. I'm using it alongside 7 other people, where 3-4 are actively contributing to it (writing).
For my work notes I've been copying links to the team docs into my personal note taking system and organizing those as I wished
No, Emvi does not support private tags. But usually you won't need many tags to identify it for everyone. I was looking for the fixed IP addresses of our local network recently and couldn't find them by searching for "IP", because it was tagged as "network". Adding IP as a new tag is beneficial for everyone.
You can bookmark, watch, or create a (private) list for stuff you look up frequently.
The Z method seems more scalable to me, since if I'm reading, I have time to spare.
1) You read waaaay more than you use. So only summarizing what you're about to use in a project takes less time total. (and even then, it's just highlighting passages)
2) The best system is the one you stick with. Yeah, in an ideal world I'd be summarizing my readings right as I'm reading it (clearly I have time to spare in those moments). I tried to do that for a while. But I just couldn't stick with it. It felt too much like homework. It was a chore. The motivation wasn't there. This PARA based system is one I can actually stick with
I sometimes daydream about a dedicated writing machine, something small, but with a full-sized keyboard so I can type quickly, and supporting nothing else but text. Sometimes I honestly think about just getting a typewriter, but it seems silly.
Has the method itself helped you in producing work that, without said method, would not have been possible or would have been much more difficult?
For zettelkasten, the one person for which the method demonstrably led to tangible results was Niklas Luhmann himself. Outside of that one data point, I'm hard pressed to find any other real-life examples.
How does Rich Hickey approach note-taking? Or John Carmack?
The problems I had with that was that it was located at work, so I couldn't access it easily off-line. Nor could I search and location a particular nugget of information particularly quickly. It was also separate from my daily journal.
In my current setup, my "3 different ways of doing X in Puppet and Ansible" has links to an Ansible page, a Puppet page, and more. Each of those Ansible and Puppet pages have a list of backlinks, so I now have a list of all the tickets that used Puppet or Ansible, and all the daily notes that involved those tickets. So I can spider through my second brain fairly quickly without searching. Which doesn't sound that important but if you don't know quite what you are looking for, then you can remind yourself by walking through the stuff associated with it.
Not the greatest example, sorry. But my "second brain" is still evolving and getting more useful. I'm excited to see what researchers come up with in this problem space!
Pictures if you want them: https://twitter.com/ZainRzv/status/1289964671563214848
Saying it’s vandalism seems a bit extreme to me—-unless we’re talking about a book borrowed from a friend or a library.
I don’t really write notes in margins much anyway. It never seemed useful to me to bind my notes directly to the pages that they come from. They become too hard to find.
I’m only really calling it vandalism with my tongue firmly in cheek–obviously anyone can do what they like with their own books :)
Now though, I'm delighted to write notes all over
The reference spectrum ranges from looking up a small, discrete nugget of information to restoring a complex mental context. At the "small nugget" end of the spectrum could be a command line invocation for a specific task, or your mother's birthday. In my experience, search works fine for this if you put in minimal effort when recording the information.
At the "complex mental context" end of the spectrum could be a project that you were immersed in six months ago and had to set aside. Documentation for this purpose takes a lot of care; it's essentially writing for another person. If you're not careful and systematic, you can end up accidentally taking a crucial aspect of context for granted and leaving it out. To choose how to structure notes for this purpose, I think of myself as a consumer. I have a lot of experience with consuming information, and I know what I like. I don't like mind maps. I like complete sentences of clear, well-structured prose, with an occasional diagram, lightly hyperlinked where it's helpful. All I need is links, basic formatting, and occasionally embedded media.
The recall spectrum ranges from memorizing specific factoids to trying to cement more complex ideas so they're available for thought later. At the factoid end is anything that could fit on a flash card, such as the definition of a word or, whoops, my mother's birthday, which probably belongs here under recall instead of under reference! At the complex end of the recall spectrum is where I would like to put the best books I read.
Again, when taking notes for recall, I think of what helps me in my experience. I like studying Anki cards for factoid recall. For the complex end, I find the effort that is best rewarded is the work of writing straightforward, well-structured prose. It's very easy to sketch graphs and diagrams that feel meaningful, but the ease is a giveaway that you aren't really mentally engaging. Writing is much harder work, because it forces you to engage with the subject in a deeper way than just splashing a vague intuition down on the page. The value is reflected in consumption: well-written prose is invaluable, while most of the images that feel like they capture part of the mental context when I have it are no help in restoring it when I don't. (Technical subjects are an outlier; diagrams are often helpful.) To be clear, since recall is the object, consumption is secondary; what is most important for me is that the act of writing well-structured prose helps cement the knowledge in my mind. It's just a nice bonus that if it doesn't stick the first time, I'll have exactly the kind of notes that are good for refreshing myself later.
Maybe it's just me, but I think discussions of note-taking techniques and structures are skewed by the desire to create something visually impressive. Nobody who is a professional at communicating information to others is using these techniques. I've never heard anybody say, I need to find a mind map to improve my understanding of the French Revolution, or Franz Kafka, or Apache Kafka. Mind maps and similar techniques have been around for many decades and have yet to prove themselves as a medium for teaching or communication. I'm very skeptical of the idea that they have some great yet-to-be-exploited utility for communication, and I'm also skeptical of the idea that their value for personal use vastly exceeds their value for interpersonal use. But this is subjective, and perhaps not everybody is the same as me.
Regarding mind maps: I've personally found them useful for thinking in the moment and brainstorming. They were also helpful for studying for a test back when I was in school (and the concepts it had to include were limited to a single chapter)
They're definitely less useful as a way to transmit information to other people though.