How Buildings Learn: What Happens After They're Built

"Thinking Forth" by Leo Brodie --> http://thinking-forth.sourceforge.net/ "How Buildings Learn: What Happens After They're Built" by Stewart Brand --> http://www.openculture.com/2015/07/watch-stewart-brands-6-pa... (http://www.openculture.com/2015/07/watch-stewart-brands-6-part-series-how-buildings-learn-with-music-by-brian-eno.html) "Programmer's Guide to the 1802" by Tom Swan --> http://www.tomswan.com/store/

I was a voracious reader of programming books prior to reading Stewart Brand's "How Buildings Learn: What Happens After They're Built." However, it was this book that made me (finally) realize that some of the best programming books are not about programming at all. As a result I've cut back drastically on my "language-specific" programming books[1] and have sought programming-relevant books instead. [1]: And I've made it a personal goal to limit the "language-specific" books to those written before 1995.

How Buildings Learn by Stewart Brand. It's about how the foundation you build something on top of determines its adaptability to change/new usage patterns

"How Buildings Learn: What happens after they're built" by Stewart Brand (ok, it's about systems and software arch) "Walt Disney: Triumph of the American Imagination" by Neal Gabler (This is awesome because the 1st third is about his multiple failures) Any David Macaulay book (breathtaking deconstruction construction) Any book on child crafts and games, vintage better. (The writing is superb and a lot of activities are excellent) Any book on network marketing (I'm not involved but have been pitched many times. The talk about funnels for recruiting is realistic).

"Becoming a Technical Leader" by Gerald Weinberg Unconventional perspective on management "How Buildings Learn" by Stewart Brand One of the best books about designing long-term architectures. Excellent coffee table book "Envisioning Information" by Edward Tufte "Walt Disney" by Neal Gabler Excellent biography of maybe the greatest imagineer ever "The Art of Software Testing" by Glenford J. Myers ~100 page classic. The central premise is that the successful test is one that finds bugs/issues not one that doesn't.