How to Increase Clojure Outreach
summary
Freshcode finds that onboarding stalls because of the Lisp curse and too many competing libraries and proposes a tooling platform that indexes social signals and usage to reduce choice friction. Research uses 52 survey responses and 14 one‑hour interviews. An open source prototype on GitHub stores data in Postgres + Metabase, already deployed as an MVP; next steps add social citation ranking (“lead rank”), an observability index and a public roadmap to measure and lower ecosystem entropy.
AI-written summary · about
chapters (19)
- 0:00Introduction
- 1:41Team
- 2:24Idea
- 3:17Survey
- 4:07Interview
- 5:28Marketing for Closure
- 6:36Product Management Model
- 8:59lisp curse
- 10:54new standards
- 11:11goal of the talk
- 11:53jobs to be done
- 13:34move somewhere
- 15:29point b
- 20:57instruments
- 22:21product management
- 23:06customer journey map
- 24:04technical platform
- 25:00next steps
- 25:50marketing
related talks
25mHow to Increase Clojure Awareness
40mGetting 50,000 Companies on Board with Clojure
16mState of Clojure
44m(Neal's) Master Plan for Clojure Enterprise Mindshare Domination
42mWhy Clojure?
55mTransforming Enterprise Development With Clojure
21mLLMs + Clojure = Who needs frameworks?
28mEvery Clojure Talk Ever