The question in the second paragraph depends on the belief that someone
could engage in pointless refactoring.
There is an implied assertion that clojure's design provides more
opportunities for someone to engage in pointless refactoring.
Disproving that someone could engage in pointless activity would miss
the point of the question. So, providing an example for that would
possibly lead to more confusion.
If the implied asssertion about clojure's design were taken to further
imply that the design is flawed in those cases, this would also be
missing the point of the question.
If cases in which clojure's design were flawed were not invented for
the purpose of pursuing this questioning. Without criticism of clojure's
design, specifics about how clojure could be used in a multitude of ways
to solve a problem, could be described by way of example. But, that
would also miss the point of the question.
So, if the image of someone engaging in pointless refactoring reminds
you of an experience that you have had, and if you can use that as the
model for a general case, how would you suggest preventing the general
case from being made actual, in the future?
Kendall
On 10/19/2013 12:35 AM, Laurent PETIT wrote:
Can you give a concrete example?
Le samedi 19 octobre 2013, Kendall Shaw a écrit :
With clojure in particular, I am having trouble not rearranging my
code to be what I think is more optimal in ways that seem probably
not practical. I've noticed myself doing that when I'm newish to
languages and apis. But, I go bonkers with clojure.
Do you have any thoughts about how to avoid that, other than Bob
Newhart's advice:
Bob Newhart-Stop It <http://www.youtube.com/watch?v=Ow0lr63y4Mw>
Kendall
--
--
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
Note that posts from new members are moderated - please be patient
with your first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- You received this message because you are subscribed to the
Google Groups "Clojure" group.
To unsubscribe from this group and stop receiving emails from it,
send an email to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
--
--
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
Note that posts from new members are moderated - please be patient
with your first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
---
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
--
ThisIsHardToRead, asIsThis. This_is_easier, unless_it_is_underlined.
This.is.easy. This-is-easy-too. Almost as easy to read as this.
--
--
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
Note that posts from new members are moderated - please be patient with your
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
---
You received this message because you are subscribed to the Google Groups "Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
