What's the solution here? After a few years you end up with huge boxes full of notes, some of which have been appended over and over? Mind maps rarely scale when done with software, paper note-taking just makes it all the more hopeless.
And really, why be so obsessive about conserving every little thought like your stream of consciousness holds some big revelation at the end? That's not how it works. Forgetting and scrapping things is an important part of organizing the mind and the output it produces. On a meta level, this book illustrates very well what happens if that doesn't work.
If we're building a system with the goal of swapping out thoughts and memories, it really has to augment the brain in some fashion. Refining relations between concepts is something the brain is already good at, it would make more sense to help it along in areas where the brain sucks: keeping lists and details. Seriously, open an Evernote account or something and don't worry too much about organization and preservation.
I'm really sorry if this sounds mean, it's not supposed to.
I clicked expecting a well thought out strategy for organizing concept maps on a large scale but instead this is some individuals idea on how best to organize their own thoughts. In fact, not once in the entire document is the term "concept map" even used which makes me think that this person has spent zero time researching established techniques on the subject.
Concept maps are great. I've used them in the past and wish I could get in the habit of maintaining them more often. If you're interested in capturing and organizing your own thoughts, I'd highly recommend you look into concept maps. This on the other hand, I'm not sure what this is and I certainly wouldn't recommend you follow it.
 PS this was not a comment on the validity of the ideas presented, just a comment on the general craziness of individual bloggers.
Madmen do tend to emphasize random words: http://zippythepinhead.com/Merchant2/merchant.mv?Screen=PROD...
(M-x yow, how I miss you.)
"keeping a map of all your thoughts has a freezing effect on the mind."
"you will be IMMOBILIZED for the duration of your commitment"
Sounds like he went mad in the attempt.
I can't help but come to the conclusion he's nuts.
Maps make amazing summarization/summary capturing tools. I used to unknowingly use them during my college days. One of the main reasons why I spent 1/10th the time yet scored the same as my classmates was maps. I would practically convert each chapter into a map, and merely crawling though a map was more than sufficient for any kind of a revision.
In our industry maps make wonderful testing tools. Lets say you want to test X, write down a map of each functionality, then write down further nodes, which basically is what could possible go wrong or right with each node(Each of this becomes a separate node). For each node you expand, stress the node bring out more test nodes until you can't stress any node anymore.
The resultant map will be nearly the best test cases you can come up with.
Now do this before you start coding, and what you will get is all the scenarios you need to handle to make the code bug free.
Additional tip, avoid using map software. Best tools for this kind of work are paper/pen or whiteboard/marker.
I've been using this strategy to write C code for embedded systems. And it works like a charm.
I agree with you on the usefulness of mapping for testing. It's definitely has helped me a lot in problem-solving. I'll throw out a few nodes that I think I need to investigate, explore each one a bit, write more items to consider, and whittle down or branch out as necessary. So after a while I resolve all the branchy, bushy sub-issues and have a reasonable game plan. Sometimes I dive into code halfway, but switch back to the map to record where I am and add new issues that come up that I need to resolve.
I also record most of the coding methods I find while working on tasks, in general form. So my mindmaps are also a web of how-to notes or a gigantic cheatsheet that details how to achieve any effect that I've previously worked through: from comparatively minor ones like the syntax for Rails migrations or opening a new window in JS, to larger ones like how to set up a Rails+postgres+nginx stack on Ubuntu, recording every action taken and issue encountered along the way. Comparisons of tools and databases and frameworks, mysterious bugs that I've run across, Sublime Text shortcuts - they all go into the maps.
I'm not sure I need to record every thought that goes through my head like the author suggests, but I think there's a lot to be said for keeping a comprehensive, organized knowledgebase.
One thought that occurred to me was that if the author had written this in the past few years, it could easily have ended up as a paid "self-help/achievement" e-book that he'd be hawking for several bucks via affiliate sales and a snazzy marketing site with sample chapters and a newsletter. It's admirable to see substantial written content being offered without all the digital marketing.
This is a very important question. Drawing Maps, especially for testing purposes depends on dumping things from your brain to paper as they come to you. The problem with Map creation software is Mouse and Keyboard, take time to draw a circle(Or at best position a circle), and write things inside the circle. Brain doesn't work in get-idea->hibernate-until-recorded->proceed mode. Our brains pretty much reach an idea, and then proceed towards the other. For that you need a quickly interacting tool. Pen/Paper, Whitboard/Marker is the best tool at this time for that kind of a purpose.
Another advantage of White board is the size. Many software teams gather create a map on a big white board, take a photograph and mail the team.
Also stuff like using Pen/Paper has separate advantages. Like putting in quick note points, or a diagram etc.
A map editor is on my todo list though. The goal is to make something where I can do exactly what I do now (type things down, little to no mousing involved, minimize time spent on the circles/organization/whatever) and shuffle the data around when it becomes more convenient. Diagrams and drawings will still be a pain though. Maybe I'll get a Cintiq or something :-)
By committing it all to paper (and presumably, by re-reading it) you fire up all those neurons periodically which will lead to you thwarting the garbage collection process. As a consequence eventually you'll either run out of room or possibly end up with mental issues (inability to acquire new stuff or inability to focus due the large number of associations running out from each thought you have).
There is a cost associated with this map making, still, I'm very much tempted to try it to see what the positive effects are.
Perhaps it is best that I just let it go and instead focus on learning new things that I really want to learn or that'd be useful for what I do/want to do?
Now if only I could selectively delete memories I could finally forget the time I ended a call to a client with "Love you, bye!".
It's exactly this. In the active mind (hyperactive, perhaps), the dataset is ever increasing and the memory banks are thrashing. On the best days, the cache is very deep. You never really know how deep the cache goes, though, so what might be the in L3 one day silently becomes /dev/null. This is a problem. (It's also, as you point out, a blessing)
A permanent store is the solution, but the brute force (write everything down) doesn't immediately solve the issue. There is no metadata in writing, so searching through papers involves full-text O(ludicrous) kind of searches. Every permanent store needs an index to be useful. It looks like the author has developed an extensive, coherent(?) way to colocate and index written information.
Considering how slowly most people can write, I'd be very curious to see how good mapping software could be used with ~300wpm stenographer-paced typing (Plover). Typing as fast as I can think into a searchable, sortable, arbitrarily small/large/nested/rearrangable/duplicable/etc medium is intriguing, to say the least.
EDIT: One more thing. The 'immobilization' that some ridicule is inherent in the medium: ink on paper. A written page is immutable and cannot show a diff. This is a bit like Purely Functional Data Structures. The 'structure' is at best just a single page, rewritten fairly quickly. As the ideas grow, sheet by sheet, editing a single page requires rebuilding the now-12-page idea. This is refactoring with pen & paper.
The only way to be 'mobile' is to either not write it down in the first place or to archive and never look at again. You're right in that rehashing old ideas thwarts gc: it's like burning an image into your screen, right into the phosphorus.
>My notekeeping system has since dramatically changed, and is now, primarily, a simple chronology with some discipline connected to it.
From the author's site.
I do record almost all my thinking. I use a very simple software called "the guide" (very lightweight outliner) and also use a mix of chronology and concept maps (basically mapping by concepts until the leaves, where each entry/page is stamped with date).
There was interesting ideas in the book (but it does look like a sample from a notebook :-)). I'll definitely take something out of it, starting with an attempt at collating my dozen of files into a global system.
"A long time ago, I stored all of my thoughts in a computer text file. It was actually an AWESOME system. The computer has so many advantages that the paper world doesn't. [...]
For all this awesomeness in the computer, you are unconsciously pulled into a problem:
ALL OF YOUR TEXT looks EXACTLY THE SAME.[...]
YES, YES! I CAN HEAR YOU COMPUTER-PEOPLE'S COMPLAINING. ``But you can use FONTS!'' But you can make it Bold! But you can make it Italics! yes! Yes! YES! I know it! You CAN do all those things.
But that doesn't make it FAST. In keeping notes, you don't want to constantly be dicking around with your UI. You want to be able to JUST WRITE.[...]
So, by contrasting with the computer, I have described the kinds of things you want to concentrate on in your notebook. USE DIAGRAMS EVERYWHERE. They are FAR better than coercive linear text. And USE VARIABLE WRITING STYLES. Write sloppy, write neat, and everything in between. It communicates to you. Use shorthand and abbreviation. Know Gregg's script? Use that when it suits you."
In general I feel that this whole text/book could use a lot of editing. It's intentional of course, as the author says himself he just spits out the text without going back. Still, at a length of >100 pages it is frustrating. Thank you anyway for posting, it is very inspiring!
Here's a Speed List: "Electronic Collaboration"
Which led me to think that in the mid term future, there will be two kinds of people, those that can program the notekeeping software of their dreams, and those that will have to rely on one written by someone else and make their process fit in. (+ those that don't see the benefits or think they can just rely on their unaugmented brain to store/structure their ideas.)
Maybe in a more distant future, when the notekeeping is integrated in the brain, everybody will be happy.
Incorrect apostrophe, Aaaaaaargh!
Mostly because that's the mistake I make most consistently.
While you take notes you don't think about it, just like when you think you don't think about it. (Taking thoughts notes is just like thinking out loud really, just it's searchable and can be structured).