Alex Miller

Sadly, one must investigate original sources, otherwise we get soundbite-knowledge. Here's a blogpost written by a core Clojure contributor that starts: "Occasionally I hear someone say that the Clojure community is against testing." (http://tech.puredanger.com/2013/08/31/clojure-and-testing/)

Or take this discussion on testing: "Finally, testing is greatly facilitated by design. Ideal testing takes some design constraints, some specification and turns it into tests as opposed to sort of embodying design inside tests. That's inside out. But again, that's something we have to work more at. Stems like Quick Check are interesting because you're basically starting with propositions about your system, which reflect the design and saying you write the tests, computer." (https://github.com/matthiasn/talk-transcripts/blob/master/Hickey_Rich/DesignCompositionPerformance.md)

http://tech.puredanger.com/2007/09/18/spelunking/

http://debasishg.blogspot.com/2009/06/code-reading-for-fun-and-profit.html

http://www.oreillynet.com/ruby/blog/2006/05/post.html
(section about "making Mongrels stable and secure"

http://news.ycombinator.com/item?id=483824

http://blog.rubybestpractices.com/posts/gregory/005-code-reading-stdlib.html