clojuredesign-podcast 2021-12-07

leifericf12:12:13

I’m only on episode 16, so there might be an episode on this topic coming up later. But in case not… When you guys start up again, I would love to hear more episode from the vein of episodes 12-15. Anything related to your early experiences with Clojure, and things that were particularly difficult to grok. For me, probably the most difficult aspect of Clojure and functional programming more broadly, is learning how to update data and “pass it around” to different parts of my program, when functions usually produce a copy of the data structure instead of modifying it in place. You touched upon this in your Tit-tac-toe series, which was great. I would love to hear more about “application state management” in particular, if that makes sense. Not sure if I’m using the correct terminology here.

✔️ 1

Drew Verlee04:12:18

while its useful to hear people talk about it, mostly so you get the common lingo, you really have to practice it then look at other solutions. 4clojure is great for this. typically the shorter the solution the "better" but read at least 5 per problem. Pick people who finished all the problems.

👍 1

Drew Verlee04:12:21

it's a bit of a "no one can be told what the matrix is" type situation. Though i'm not saying clojure is the matrix of it's day. idk maybe. i'm here at least 🙂

sebastian19:12:33

I agree. You have to bang your head against the wall to learn how to use thread macros ans let bindings effectively. I am currently doing advent of code in Clojure where I learn a lot. And there are always a lot of solutions to learn from. Also a couple of video streamers I like very much.

sebastian19:12:51

For me it is a good combination. Grok the problem, solve it myself (sometimes very crude) and learn from others.

2021-12-07

Channels