If you let one of your houseplants completely dry out and then try to bring it back to life by dumping a large amount of water in the pot, you will end up with water all over the floor. Dry soil cannot absorb moisture quickly so the water you pour in will run through the soil, out the hole in the bottom of the pot, into the saucer the pot is resting on, over the sides, and onto the floor. Damp soil can absorb moisture far more quickly that dry soil. Readers are like that too. Experts can absorb much more information much faster than novices. Thus experts read far more than novices do.
‘Any technology you use should be “Googlable”‘. These are the words of Bill Scott, VP Engineering, Merchant | Retail | Online Payments at PayPal, as reported by the amazing Sarah Maddox. (I say amazing because Sarah manages to lucidly and intelligently blog just about every conference session she attends. Having just helped cover the LavaCon conference, and not achieving anything like Sarah’s level of productivity or swiftness, I can only marvel at her ability.)
I was astonished at Sarah Maddox’s statement, in her guest post Why don’t technical writers use wikis — or do they? on I’d Rather be Writing, that wikis are not good at topic-based writing. Huh? Wikis are all about topic-based writing. In fact, it is the only type of writing they really support.
What’s wrong here? It certainly isn’t that Sarah does not understand wikis. If you want to know about using wikis in technical documentation, Sarah is the first person you want to talk to. If anyone knows wikis, it’s Sarah. She’s even written a book on the subject. What’s wrong, apparently, is that the term “topic-based writing” seems to have been corrupted or co-opted and robbed of its proper meaning. This is serious, and it needs to be fixed.