On Aug 9, 2017 7:46 PM, "Luc" wrote:
The other unpleasant option to climb the learning curve asap is to end up
with a deadline to spit out a product
I did it, 5 months of pure Hell
yes, but now you are a badass, no? it's the only way.
After that the pain went
The other unpleasant option to climb the learning curve asap is to end up with
a deadline to spit out a product
I did it, 5 months of pure Hell
After that the pain went away, either my brain adapted or my nervous system
could not feel it anymore,
can't remember 藍
Luc P.
--
You received
On Aug 9, 2017 1:43 PM, "Andy" wrote:
This feels like a different world.
There's a reason for that. The conceptual space of languages like clojure
is indeed radically different than the conceptual space of "imperative"
languages. Think Turing (or maybe VonNeuman) machine
Hi, Andy.
It took me up to 8 months before I switched my brains to functional way of
thinking.
When I started to learn Clojure, first code was in Clojure syntax but fully
imperative style.
Everything in Clojure was inconvenient and horrible. I didn't understand
why people like Clojure.
But,
Hi Andy!
Honestly, there's something very lovable and addictive about working in
Clojure and lisp in general, but I would caution against trying to use it
as a silver bullet, and generalizing it to improving general
'problem-solving' skills might be a bridge too far.
I think what lisp does do is
Thanks @Paulus, @Gary and @Peter,
Rearranging the process to let go of the head is good advice.
I believe the problem (should I need to keep all elements in memory) may
ultimately be lazy collections inside the maps I'm producing.
I saved 1,917 of these elements to disk and it took only 3
This feels like a different world.
Has anyone experienced a sharp increase in their problem solving abilities
after switching to Clojure?
I have been working my way through Living Clojure an Oreilly book.
My curiosity got the better of me and I wondered if anyone here had some
suggestions for