Ep 038: How do I convince my coworkers to use Clojure?
We recall our own experiences evangelizing Clojure and give practical advice from the trenches.
Ep 037: What Advice Would You Give to Someone Getting Started With Clojure?
We trade off giving practical tips for intrepid learners reminisce about our own paths into Clojure.
Ep 036: Why Do You Recommend Clojure?
We take turns sharing our favorite reasons, and we can't help but have fun riffing on how enjoyable Clojure is to use.
Ep 035: Lifted Learnings
Christoph and Nate lift concepts from the raw log-parsing series.
Ep 034: Break the Mold
Christoph finds exceptional log lines and takes a more literal approach.
Ep 033: Cake or Ice Cream? Yes!
Nate needs to parse two different errors and takes some time to compose himself.
Ep 032: Call Me Lazy
Christoph finds map doesn't let him be lazy enough.
Ep 031: Eager Abstraction
Nate finds that trouble comes in pairs.
Ep 030: Lazy Does It
Christoph's eagerness to analyze the big production logs shows him the value of being lazy instead.
Ep 029: Problem Unknown: Log Lines
Nate is dropped in the middle of a huge log file and hunts for the source of the errors.
Ep 028: Fail Donut
Christoph has gigs of log data and he’s looking to Clojure for some help.
Ep 027: Collected Context
Nate and Christoph reflect on what they learned during the Twitter series.
Ep 026: One Call to Rule Them All
Christoph thinks goals are data, not function names.
Ep 025: Fake Results, Real Speed
Nate wants to experiment with the UI, but Twitter keeps getting the results.
Ep 024: You Are Here, But Why?
Christoph needs to test his logic, but he must pry it from the clutches of side effects.
Ep 023: Poster Child
Nate gets messy finding ingredients for his algorithm cake.
Ep 022: Evidence of Attempted Posting
Christoph questions his attempts to post to Twitter.
Ep 021: Mutate the Internet
Nate wants to tweet regularly, so he asks Clojure for some help.
Ep 020: Data Dessert
Christoph and Nate discuss the flavor of pure data.
Ep 019: Dazed by Weak Weeks
Nate wants to see more than data structures in a REPL.