Work Through Conversations
A compact set of interview sequences that reflect how technical work, community stewardship, and long-horizon engineering practice overlap.
Architecture and Resilience
Conversations about system shape, operational boundaries, and decisions that hold under change.
Interviewee: Rich Hickey creator of Clojure
Video description: Rich Hickey is the creator of the Clojure programming language, a dialect of Lisp that runs on the Java Virtual Machine (JVM). He released Clojure to the Lisp mailing list and it gained popularity through word of mouth and online communities. Hickey believes that the fact that Clojure runs on the stable and well-established JVM has contributed to its success, as it allows users to try something new while still maintaining a connection to the technologies they are familiar with. Hickey also discusses the importance of simplicity and concision in programming languages and the role of language design in enabling programmers to solve problems more effectively.
Community as a Technical System
Interviews that treat user groups and conferences as feedback systems for shared practice.
★ Transcript Available
Interviewee: Ray Hightower
Topic: ChicagoRuby
★ Transcript Available
Interviewee: Brian Ray
Topic: ChiPy
Video description: Brian Ray (@brianray) took the time to sit down before the April 2012 ChiPy (pronounced Chippy) and chat about the Chicago Python community.
Interviewee: Scott Seely
Topic: Lake County .NET User Group (LCNUG)
Video description: Scott Seely runs a .NET users' group up in Grayslake, IL. He's also extremely active in the Chicago-land Microsoft Developer community that Microsoft recognized him as a Regional Director. He explains why he founded LCNUG and what exactly is a "Regional Director".
Craft and Mentorship
Discussions on apprenticeship, deliberate practice, and how experience is transmitted across teams.
★ Transcript Available
Interviewee: Adewale Oshineye
Video description: Interview with Adewale Oshineye at Software Craftsmanship North America (SCNA) on developer advocacy, documenting and sharing learning, and finding the right communities where technical contribution adds value.
