Fork me on GitHub
#clojure-uk
<
2021-03-30
>
dharrigan05:03:57

Morning Peeps!

danm07:03:31

Ahoy hoy

jiriknesl11:03:33

I do a lot of interview recently and I must admit, lots of people get to Clojure thanks to universities. And thanks to SICP. Which is something I wouldn’t expect at all. My experience is, Clojure folks are often highly senior people who know all those pains Clojure is addressing (often by not implementing something), while some people get to Clojure fairly in the early stage in their career. I am sad, in my university, it was a lot about C-like languages and we haven’t got a lot into FP (which might be caused by the fact it was an offspring of electrotech faculty and we have spent more time speaking about how electron goes in a wire than speaking about functional programming).

Mario Giampietri13:03:40

"Clojure folks are often highly senior people who know all those pains Clojure is addressing" AKA old grumpy devs 😄 ❤️

jiriknesl14:03:34

Grumpy for a good reason. The only missing part is that Clojure still has nil. But of course, as Clojure is embracing underlying platform, and if the platform has nil, Clojure must have nil too. At the same time, when operating with numbers, clojure.lang.Ratio is a default (an awesome one) output of lots of numeric operations which isn’t in particular embracing underlying platform (it’s way more Scheme-ish than JVM-ish). So maybe sometimes it matters and sometimes it doesn’t.