Every Clojure Talk Ever
summary
A satire of adopting Clojure at a startup: architecture piles on Kafka and RabbitMQ while the chosen datastore is Google Sheets database, memcached replicas and a load balancer buy time, CI is a laptop cron job, and a failed REPL demo repeats. Language experiments produce a public thread-first-thread-last-backwards? macro and an encapsulation layer driven by a visibility map that returns nothing. Claimed wins are three percent reduction then later a four percent reduction in lines of code after adding hundreds of thousands of XML lines.
AI-written summary · about
chapters (8)
- 0:00Intro
- 2:13Random Corp
- 2:41Architecture
- 5:16Challenges
- 9:21Learning Closure
- 11:34Macros
- 13:50Ripple
- 24:34Closer
related talks
34mClojure by neophyte
21mA Clojure Carol: Three Clojure Web Development A-Ha Moments
31mClojure at 4,000 msg/s-What We Learned, Loved, and Loathed
31mLightning Talks
40mFun with Functional Programming in Clojure
43mDoing Data Science with Clojure
44m(Neal's) Master Plan for Clojure Enterprise Mindshare Domination
01h 15mEffective Programs - 10 Years of Clojure