Each week, we discuss a different topic about Clojure and functional programming.
If you have a question or topic you'd like us to discuss, tweet @clojuredesign, send an email to [email protected], or join the #clojuredesign-podcast channel on the Clojurians Slack.
This week, the topic is: "2019." We look back at the past year and highlight our favorite episodes.
"2020 is the year of perfect hindsight.""Even we are surprised at what we recorded.""Mutation is like weak bricks in your solution tower, they could fail you at any time.""The Twitter API is just a whole bag of side effects.""Programming without I/O is just warming your room.""Not everything does all the things perfectly in all the ways.""Complexity really is the killer in long term projects."The REPL Series (12-14)012: Embrace the REPL014: Fiddle with the REPLThe Time Tracking Series (15-20)016: When 8 - 1 = 6018: Did I Work Late on Tuesday?The Twitter Poster Series (21-27)022: Evidence of Attempted Posting024: You Are Here, But Why?The Donut Logs Series (28-35)032: Call Me Lazy034: Break the MoldAdvocacy Episodes (36-39)036: Why Do You Recommend Clojure?037: What Advice Would You Give to Someone Getting Started With Clojure?038: How do I convince my coworkers to use Clojure?039: Why use Clojure over another functional language?040: Should I use lein, boot, or tools.deps?Data Episodes (41-42)041: Why do Clojurians make such a big deal about immutability?042: What does it mean to be 'data-oriented'?Questions from our listeners (43-48)046: When is Clojure not the right tool for the job?047: What is "nil punning"?048: Help! How do I fix my REPL?Word! Word! Word! Series (aka Nountober) (49-52)049: Keywords! Keywords! Keywords!052: Functions! Functions! Functions!053: How can I save my data from serialization?054: The Forest in the Trees055: Sets! What are they good for?056: Opt-In Complexity057: Clojure/Conj 2019 RecapReduce, Reducers, and Transducers (58-61)061: Transcendental Transformations