History of Software Craftsmanship in Chicago: The Oral Record
Between 2006 and 2015, Chicago transformed from an enterprise IT town dominated by financial trading desks and legacy Java monoliths into one of the most vibrant software engineering ecosystems in North America.
An organic developer uprising known as the Software Craftsmanship Movement catalyzed this transformation. Frustrated by “Agile-in-name-only” management bureaucracy and academic conferences that ignored real-world coding practice, a dedicated circle of practitioners built their own communities: Software Craftsmanship McHenry County (SCMC), Chicago Software Craftsmanship, and Software Craftsmanship North America (SCNA).
Chapter 1: The Frustration & The Catalyst (2006–2008)
By 2006, enterprise consulting firms were diluting the original promise of Extreme Programming (XP) and Test-Driven Development (TDD). “Agile” had become synonymous with daily standups and burndown charts, while actual code quality, refactoring, and automated testing were sidelined.
In Chicago, Dave Hoover (co-founder of Obtiva) and early software craftsmanship advocates began hosting informal coding katas outside business hours. Instead of listening to lectures, developers brought laptops, paired up, and practiced TDD exercises in Ruby and Java.
Chapter 2: “Too Practical”: The Rejection That Launched SCNA
In 2009, local practitioners submitted talk proposals to traditional academic and enterprise software conferences. The feedback came back blunt: “Your talks are too hands-on. Showing live refactoring, TDD katas, and ORM internals is too tactical and practical for a professional conference.”
“They told us live pairing, TDD katas, and unit test refactoring were ‘too practical’ for a stage. We decided right then: if mainstream conferences won’t show real engineering practice, we will build a stage dedicated entirely to it.”
That rejection became the rallying cry across the Chicago developer community, leading organizers to launch the first Software Craftsmanship North America (SCNA) conference. It was a landmark gathering that rejected slides-only presentations in favor of live code execution, pairing, and architectural debate.
Obtiva and 8th Light organized that first SCNA together, and I had joined Obtiva that August. Energized by the movement’s focus on deliberate practice, Ryan Gerry and I founded Software Craftsmanship McHenry County (SCMC) in the northwest suburbs, partnering with 8th Light leaders Steve Kim and Jim Suchy to bring hands-on katas, peer pairing, and practitioner keynotes to the suburban developer community.
Chapter 3: Keynotes & Community Leaders (2010–2012)
The Chicago movement brought together iconic leaders:
- Robert “Uncle Bob” Martin: Delivered seminal keynotes on clean architecture, professional ethics, and code legibility at SCMC and SCNA.
- Dave Hoover: Pioneered software apprenticeship programs in Chicago that trained hundreds of junior developers in TDD.
- Steve Kim & Jim Suchy: Hosted monthly downtown Chicago pairing sessions at 8th Light, bridging urban and suburban communities.
- Andy Maleh: Guest presented Software Craftsmanship VS Software Engineering at SCMC, demonstrating Glimmer DSL and SWT desktop tooling on the JVM.
- Igor Polevoy: Demonstrated lightweight ActiveRecord ORM patterns for Java (ActiveJDBC) at SCMC to streamline enterprise backends.
- Ray Hightower: Co-organized SCNA and ChicagoRuby, connecting Midwest developers with national keynote speakers.
Robert “Uncle Bob” Martin presenting his talk on “State” and clean boundaries from the SCNA 2010 stage in Chicago.
Chapter 4: The Economic Dividend (2012–2015)
The craftsmanship movement created the talent engine for Chicago’s tech boom. Companies like Groupon, Obtiva, Braintree, Belly, ActiveCampaign, and BenchPrep grew rapidly because they hired developers trained in rigorous TDD, continuous deployment, and clean architecture.
Fishbowl Circle (August 2011): Chicago practitioners in an open-space circle discussing apprentice mentorship and sustainable code quality in a downtown loft.
By treating code quality as a core business asset rather than a secondary concern, Chicago engineering teams achieved high release safety and rapid feature velocity without accumulating unmanageable technical debt.
Read the full interactive monograph and primary media archive at https://just3ws.github.io/chicago-craftsmanship/.