Chris Houser discusses stack traces in Clojure and introduces a library for investigating activity across multiple threads and servers, plus a technique for reproducing race conditions.
David McNeil introduces a model for thinking about Clojure evaluation through code samples with the purpose for an easier understanding and writing of macros.
Luke VanderHart introduces Domina – DOM manipulation library –, explaining a new way of writing dynamic web pages.
Creighton Kirkendall introduces Google Closure Tools and the challenges writing a ClojureScript library.
Tyler Jennings presents how he ended up choosing Clojure, how he is using a Ruby tool-chain in Clojure, plus advice on introducing Clojure to a team.
Jim Duey advises on solving a problem by dividing it in smaller requirements that are dealt with, then using DSLs to compose results into one big solution. Code samples in Clojure.
Richard P. Gabriel expands upon “Mixin-based Inheritance” by G. Bracha and W. Cook, observing that software engineering precedes science and incommensurability can be used to detect paradigm shifts.
Craig Andera explains how some of the main Clojure constructs – namespaces, vars, symbols – are processed during the read and eval phases of the compilation.
Bill Caputo discusses adopting continuous testing for Clojure, what are the goals of such a practice, how it differs from other languages, practical considerations (tools, setup) and a demonstration.
Aaron Bedra shows code samples for writing Clojure tests using the test.generative framework, explaining why this framework and testing are useful.
Stuart Sierra discusses using a data-oriented programming approach in order to create programs that are easier to write and test. The session is accompanied with Clojure code samples.