| Thanks for posting this. 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.