Re: Compulsive over-optimization

2013-10-22 Thread Kendall Shaw
Optimizing too much for readability, can't be well worth doing, I think. It's a contradiction in terms. Watching out for changes that make the code shorter instead of more readable seems like useful advice and maybe a sign that I am "optimizing" too much. I'm pretty sure I could figure out a wa

Re: Compulsive over-optimization

2013-10-22 Thread Alex Baranosky
Well said Niels. As far as performance optimization. Imo that's premature until you profile. On Tue, Oct 22, 2013 at 2:42 AM, Niels van Klaveren < niels.vanklave...@gmail.com> wrote: > I can imagine this behavior. Unlike premature performance optimization, > readability / terseness are well wor

Re: Compulsive over-optimization

2013-10-22 Thread Niels van Klaveren
I can imagine this behavior. Unlike premature performance optimization, readability / terseness are well worth optimizing for when learning Clojure, as long as you value readability over terseness to keep well away from code golf territory. With Clojure, I always have the idea that things coul

Re: Compulsive over-optimization

2013-10-20 Thread Alex Baranosky
Kendall, Refactoring is valuable especially when starting out, so that you can learn how to represent patterns well in Clojure, imo. On Sun, Oct 20, 2013 at 10:59 AM, Kendall Shaw wrote: > I might have come off as obnoxious. So, sorry about that. > > Now that I think about it some more, the que

Re: Compulsive over-optimization

2013-10-20 Thread Kendall Shaw
I might have come off as obnoxious. So, sorry about that. Now that I think about it some more, the question probably doesn't have a procedure to suggest as an answer. It's in the same class as like "how do I start" or "how can I stop asking so many questions". Kendall On 10/19/2013 03:05 PM,

Re: Compulsive over-optimization

2013-10-19 Thread Softaddicts
I read your post three times and now I need to get a couple of fuses replaced :) Holy smoke, it's Saturday man ! Most of us are probably trying to recover from the work week, give us a chance :))) Luc P. > The question in the second paragraph depends on the belief that someone > could engage i

Re: Compulsive over-optimization

2013-10-19 Thread Kendall Shaw
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 acti

Re: Compulsive over-optimization

2013-10-19 Thread Laurent PETIT
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

Re: Compulsive over-optimization

2013-10-18 Thread Kendall Shaw
The premise is that it is rearranging that is not worth the effort. I guess I will try estimating how long I would spend on a similar task using something I am more familiar with and then trying to keep within some proportion of that effort. Kendall On 10/18/2013 07:41 PM, John D. Hume wrote

Re: Compulsive over-optimization

2013-10-18 Thread John D. Hume
What kind of optimal do you compulsively rearrange for? Performance? Readability? Amusing terseness? On Oct 18, 2013 6:20 PM, "Kendall Shaw" wrote: > 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 practic

Compulsive over-optimization

2013-10-18 Thread Kendall Shaw
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