That's how Lee Hopkins describes the new Wikipatterns book, and I'm deeply flattered that he feels that way. Why? Because that's exactly how I wanted it to come across to people who would use it to guide their wiki adoption. When you take on a serious project like introducing and growing adoption of an enterprise software tool, you want serious, concrete advice that you can rely on. Hype, too much flowery language, and "excessive verbiage" just get in the way of the message and dilute its impact. So if you want a practical guide that you can read in one sitting, and will refer to over and over, then Wikipatterns might just be for you.
Link to original post