4 ms·
The huge problem with taking out all the stories is that the book becomes quicker to read, but much drier and less memorable. Stories make things stick in the
by swombat 15y ago
The huge problem with taking out all the stories is that the book becomes quicker to read, but much drier and less memorable.
Stories make things stick in the reader's mind, as well as providing additional angles to explain complicated concepts by example.
As a simple example, I could explain that you shouldn't call for help when you don't need it, because people will start to ignore you and then you won't get the help when you do need it... or I could tell you the story of the boy who cried wolf. Which one do you think you'll remember in a year?
Stories are powerful stuff.
- hello_moto 15y agoI hear you and agree to what you said given the context (complicated concepts, etc). But somehow I doubt these books (Lean Startups, Checklist Manifesto, Agile) are complicated concepts. Derivatives and HFT might be considered complicated concepts. Quicker to read but if it is to the point (especially bullet points) might lead to quicker to remember. I've seen many bloggers claimed they read a 350 pages book in 2 sessions, 1 session, a flight to Chicago (5 hours?) and claiming that they "get it" is a bit questionable. Perhaps they know where the points are and skip the irrelevant parts? If that's the case, why not make the book slimmer? :D But, it is what it is: there's probably a demand from society expecting their money to be worth. I'm asking for a separation of the theory and the application. Start the book with the theory first and finish it with the application (business-case, use-case) to avoid intermingling the concept and the examples.