Live data from Hacker News

(next Rich)

clojure.org

151–158 of 158 posts

Re: (next Rich)

#151

Rich's simple made easy is the best programming video I've ever seen, and is ultimately I think what so many engineers need to "grok" to unlock better coding. I'm the "most senior" engineer (chief architect) in a company of more than a thousand engineers, and I recommend it to every junior who asks how to get better. I will also say I used clojure + aleph to write the only significant application I ever released whic…

I stared leaning it a few agos.

1 (the last result) 2 (the result two expressions ago) *3 (the result three expressions ago)

oh yeah. I cant see this giving problems in the future....

Re: (next Rich)

#152

Earlier quoted context omitted.

And yet, the word Hickey coined, "complect", is silly at best, and a gatekeeping obstacle to outsiders/newcomers at worst.

Funnily enough, your complaint here is that although it may be simple, it is not necessarily easy, while the talk is an argument that we should prefer simplicity even at the cost of some (temporary) un-ease.

I'm not sure how you got that impression from my comment.

But for the sake of argument, I'm saying "complect" is neither simple *nor* easy. It's obviously not easy since it's unfamiliar. But nor is it simple, or to be really precise, no simpler than alternatives, since it doesn't conceptually improve on plain words and phrases like "complicate", "intertwine", "mix up", "separate", "tease apart", etc. It adds nothing, really.

Your comment kind of highlights some of the errors many take away from "Simple Made Easy": that ease is in opposition to simplicity and/or that they are completely orthogonal.

Re: (next Rich)

#154

Rich's simple made easy is the best programming video I've ever seen, and is ultimately I think what so many engineers need to "grok" to unlock better coding. I'm the "most senior" engineer (chief architect) in a company of more than a thousand engineers, and I recommend it to every junior who asks how to get better. I will also say I used clojure + aleph to write the only significant application I ever released whic…

I stared leaning it a few agos. 1 (the last result) 2 (the result two expressions ago) *3 (the result three expressions ago) oh yeah. I cant see this giving problems in the future....

Your message is undecipherable. I have no idea what you’re trying to say.

Re: (next Rich)

#157

Rich's simple made easy is the best programming video I've ever seen, and is ultimately I think what so many engineers need to "grok" to unlock better coding. I'm the "most senior" engineer (chief architect) in a company of more than a thousand engineers, and I recommend it to every junior who asks how to get better. I will also say I used clojure + aleph to write the only significant application I ever released whic…

I stared leaning it a few agos. 1 (the last result) 2 (the result two expressions ago) *3 (the result three expressions ago) oh yeah. I cant see this giving problems in the future....

Assuming you're referring to *1, *2, *3 and *e, these are only defined within the REPL and are never used in real programs.
Post reply on HN