(Neal's) Master Plan for Clojure Enterprise Mindshare Domination
summary
Plans to win Enterprise mindshare focus on reducing risk and sneaking Clojure into existing stacks: push CTO-friendly signals (hireability, stability), seed get Clojure.jar everywhere by piggybacking on tools like Cucumber and Gradle, and target practical problems—build a polished REST-integration DSL, a better O/R mapping approach, and a usable rules engine. Encapsulate Java libraries with clean Clojure wrappers (example: a Clojure front end for Akka), produce tutorial bundles and school outreach, and stay relentlessly on-message.
AI-written summary · about
chapters (41)
- 0:00Intro
- 2:00Welcome
- 3:10Three topics
- 3:22How do things become popular
- 3:57No Fluff Just Stuff
- 4:22Build Your Own Technology Radar
- 5:00Hold Ring
- 5:42Build Two Radars
- 6:12Litmus Tests
- 6:29CTO Litmus Tests
- 9:52Create Closures Everywhere
- 11:21Cone Contest
- 11:54Make Closure commonplace
- 12:35Neals clipper history
- 13:21Neals technology stack
- 13:51Visual Objects
- 14:11Delphi
- 14:31Productivity Pirates
- 15:19Web Frameworks
- 17:01Breaking and Entering
- 21:11Make it Popular
- 21:41Propaganda
- 22:08Stay on message
- 23:09Knitted Castle
- 23:44Charlie Nutter
- 24:47Building a bridge to popularity
- 24:57The most significant technical advantage
- 25:23Prove it
- 25:59Know your enemies
- 26:39Scala has a head start
- 27:25Selling first alternate language to Java
- 28:03A rising tide raises all ships
- 28:30Other communities are not going to make it easier
- 30:06How to penetrate the enterprise
- 32:11Does anybody have questions
- 32:34Should we bother the enterprise
- 34:21Mollifying
- 35:28Automation
- 36:16Clojures baggage
- 38:42People they want
- 40:34Build a bridge
