Growing Clojure inside the company
summary
A concrete plan for growing Clojure inside a company: run a one-to-three month bootcamp (example six-week schedule: week 1 language, weeks 2–3 paired problems, week 4 interview kata, final weeks company-domain project), keep a ~1:4 teacher ratio, teach structural editing and REPL workflow, force tests and idioms, automate editor and REPL setup, fund training from hiring budget, convert learners to productive devs, enforce conventions, linting and GC tuning, use zero-downtime rolling deploys, extract shared libraries and tighten API schemas.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 1:20Challenges
- 5:48Training
- 14:30Providing Support
- 15:26Supporting Intermediates
- 15:42Pairing
- 17:18Debugging
- 18:05Enabling Success
- 18:25New Problems
- 18:41Spiderman
- 19:32Conventions
- 21:08Deploys
- 22:46Success stories
- 23:05Selling Clojure
- 23:50Recruiting
related talks
45mTeaching Clojure Together
08mActivating a Clojure Community
44m(Neal's) Master Plan for Clojure Enterprise Mindshare Domination
41mTeaching Clojure
31mClojureBridge | Jennifer Eliuk - Apprenticeships, I Implore You
27mHow to Increase Clojure Outreach
25mHow to Increase Clojure Awareness
28mEvery Clojure Talk Ever