Fork me on GitHub
#clojuredesign-podcast
<
2019-08-03
>
jrwdunham16:08:22

@neumann @nate I really appreciate your podcast. In terms of describing code and/or challenging FP/Category Theory concepts in the audio-only medium, I think the LambdaCast podcast does a good job of that. If you haven't listened to it, it's basically a master, an intermediate, a novice, and a baby novice going over and over a single concept for an entire episode—having the novice viewpoints in there really helps them to cover things that might seem obvious to the master. Though their entire format is quite different from yours, it might inspire some useful ideas/strategies.

nate17:08:06

@jrwdunham great, thanks for the tip. I'll definitely check out the LambdaCast. Any episode in particular that I should start with?

jrwdunham18:08:37

@nate they are kind of organized like a book: starting from fundamentals and building on concepts solidified in previous episodes... That said, I think starting with 12, and moving on to the 16-18 series, if interested (monoids to monads, through functors and applicative functors) might be a good way to go.

nate19:08:15

Great. Thanks for the recommendation.

genekim19:08:46

@jrwdunham Holy cow. Thank you for the LambdaCast recommendation. I’m four episodes in, and absolutely loving it. I wish I had known about this, and that @nate’s podcast had been around 3 years ago when I was learning Clojure. (Both sort of remind me of Philosophy Talk show on NPR. I haven’t listened to a lot of them, but I loved the ones I’ve listened to. Combination of deep philosophical principles and the pragmatic. :) These are such utterly superb and wonderful resources for beginners. Kudos @nate on the podcast!

👍 4
nate19:08:42

simple_smile Thank you for your support!

jrwdunham19:08:56

On a different note, your Ep 037 “The problem isn’t the code that I’m writing, the problem is with my approach” advice helped me on a problem I was working on. I've been writing a Gherkin library in Clojure and coming from the Python world, I was initially creating more of a command-line tool that would discover Gherkin feature files and Clojure step implementations and then execute the features as tests, using the Clojure steps files as implementation. However, I was running into classpath difficulties with loading arbitrary Clojure code for the step functions. Then your discussion made me think "Hey, maybe this isn't the Clojure way to do that..." So now I've switched strategies to make it more of a Gherkin library that other projects can depend on: the main project can now choose a la carte which namespaces to use, including the CLI namespace, if it wants.

nate22:08:30

Wow, that's great. Thanks for sharing how our advice helped you.

genekim19:08:46

@jrwdunham Holy cow. Thank you for the LambdaCast recommendation. I’m four episodes in, and absolutely loving it. I wish I had known about this, and that @nate’s podcast had been around 3 years ago when I was learning Clojure. (Both sort of remind me of Philosophy Talk show on NPR. I haven’t listened to a lot of them, but I loved the ones I’ve listened to. Combination of deep philosophical principles and the pragmatic. :) These are such utterly superb and wonderful resources for beginners. Kudos @nate on the podcast!

👍 4