It is obvious to me now that I am still very much a newbie to Clojure!
On Fri, Oct 2, 2015 at 11:51 AM, Colin Yates wrote:
> +1 to pipe-lines of immutable data transformations. That was the biggest
> paradigm shift for me coming to FP and made the world a much better place.
>
> On 2 Oct 2015, at
+1 to pipe-lines of immutable data transformations. That was the biggest
paradigm shift for me coming to FP and made the world a much better place.
> On 2 Oct 2015, at 16:41, Gary Trakhman wrote:
>
> There are a lot of strategies to deal with the coupling of reuse. I find
> that using pure fu
There are a lot of strategies to deal with the coupling of reuse. I find
that using pure functions makes it easy to split off responsibilities after
the fact and add multiple entry points (the hard thing becomes naming those
functions). Eventually a new 'essence' of the abstraction will show itse
It might just be me, but I also find the cost of the explicit coupling that is
re-use is often far more expensive than any saving offered by re-use of a bunch
of text. I also find this _more_ expensive in Clojure than Java as refactoring
in Java was pretty robust (IntelliJ is incredibly powerful
Refactoring for reuse is a kind of early optimization? Agreed! Generally
for me it waits until the second or third rewrite, as by then I have a bit
of an idea about where I am headed with the code.
OTOH, I finally realized that when I don't know where I am going with
something, keeping the logic i
lasses becomes much
> easier, and the need to refactor the code is greatly diminished. And writing
> reusable functions is much easier than writing reusable classes.
>
>
>
> from https://github.com/laforge49/aatree/wiki/Towards-Greater-Code-Reuse
> <https://github.com/l
easier than writing reusable classes.
>
>
> from https://github.com/laforge49/aatree/wiki/Towards-Greater-Code-Reuse
>
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
code becomes much clearer, defining new classes becomes
much easier, and the need to refactor the code is greatly diminished. And
writing reusable functions is much easier than writing reusable classes.
from https://github.com/laforge49/aatree/wiki/Towards-Greater-Code-Reuse
--
You received
