Re: Advice on introducing a Java dev to Clojure

mentioning between one and three interesting facts about >>> it. They will be watching Rich Hickey talks in a minute. >>> >>> Unless a programmer is adventureous and likes to try out new languages >>> or has decided that he "wants to learn something new&quo

Re: Advice on introducing a Java dev to Clojure

Thank you for these suggestions, Paul. Especially the last bit about a working system. I'll look for an opportunity to do that. I loved your conj talk. Incredible! On Thursday, July 23, 2015 at 6:04:42 AM UTC-7, Paul deGrandis wrote: > > I have had success here with a few approaches. > > For eve

Re: Advice on introducing a Java dev to Clojure

nding time on improving evangelizing and elevator pitching is > still well spent if you want to convince managers. I find Rich Hickeys > rationale on the Clojure page is a great starting point and there is also a > great talk by Paul deGrandis (Clojure minimizes risk). > > On Fr

Re: Advice on introducing a Java dev to Clojure

neither are simply > plugin replacements for ‘a database’. > Me neither. My one thought on this is that with Datomic the event schema could be more flexible. The event name is just a tag on the transaction. > That’s probably enough; I would love to do this properly in a blog > post/

Re: Advice on introducing a Java dev to Clojure

n't have any words of wisdom on how to evangelize Clojure, but I > am glad to see someone else noted the parallels between CQRS and a more > functional style of programming. > > Cheers! > -Matt > > On Saturday, July 11, 2015 at 2:47:31 PM UTC-7, Johanna Belanger wrote:

Re: Advice on introducing a Java dev to Clojure

words of wisdom on how to evangelize Clojure, but I > am glad to see someone else noted the parallels between CQRS and a more > functional style of programming. > > Cheers! > -Matt > > On Saturday, July 11, 2015 at 2:47:31 PM UTC-7, Johanna Belanger wrote: >> &g

Re: Advice on introducing a Java dev to Clojure

utiful way of showing power of Clojure and ClojureScript. > > https://github.com/shaunlebron/t3tr0s-slides > > Have fun! > -- > Juvenn Woo > Sent with Sparrow <http://www.sparrowmailapp.com/?sig> > > On Saturday, 11 July, 2015 at 1:24 pm, Johanna Belanger wrote: &

Re: Advice on introducing a Java dev to Clojure

s everyone for your advice. On Thursday, July 9, 2015 at 3:20:23 PM UTC-7, Johanna Belanger wrote: > > Hi :) > > I've recently broached the subject of Clojure with another dev in my > organization, and his response was basically "What's Clojure"? and I'm not

Re: Advice on introducing a Java dev to Clojure

sibly > rewrite to Java, if the truck thing was to happen. > > Erik. > -- > i farta > > Den 10. jul. 2015 kl. 07.25 skrev Johanna Belanger >: > > That's a good read, Sean. > > I'm a dedicated departmental programmer, and to be effective in my &

Re: Advice on introducing a Java dev to Clojure

of using Clojure for all of my coding, but only a few particular cases. Thoughts? On Thursday, July 9, 2015 at 8:04:11 PM UTC-7, Sean Corfield wrote: > > On Jul 9, 2015, at 7:58 PM, Johanna Belanger > wrote: > > I should say, because I'm worried this came across wrong, that

Re: Advice on introducing a Java dev to Clojure

I should say, because I'm worried this came across wrong, that I don't expect him, or anyone, to learn Clojure for my sake, but only if they find value in it. That's why I'm looking for a simple way to showcase the value. On Thursday, July 9, 2015 at 5:54:51 PM UTC-7, Jo

Re: Advice on introducing a Java dev to Clojure

Lol, that's an interesting reply. I'm suspecting it's a warning. Care to expand? On Thursday, July 9, 2015 at 6:16:25 PM UTC-7, raould wrote: > > > and I need to be 10 times more productive. =) > > you mean, after your 2 week ramp-up time, right? > -- You received this message because you are

Re: Advice on introducing a Java dev to Clojure

Thanks Sean =) On Thursday, July 9, 2015 at 5:27:16 PM UTC-7, Sean Corfield wrote: > > On Jul 9, 2015, at 5:22 PM, Colin Yates > > wrote: > > There are two bookd you might want to give them, Functional Programing > for OO by Brian Marick and another one I can't remember the title of but > some

Re: Advice on introducing a Java dev to Clojure

e two bookd you might want to give them, Functional Programing for > OO by Brian Marick and another one I can't remember the title of but > something like Functional Programming in Clojure and Scala. They might both > help provide an on-ramp. > On 9 Jul 2015 23:20, "Johan

Re: Advice on introducing a Java dev to Clojure

Thank you, Ralf! On Thursday, July 9, 2015 at 3:28:14 PM UTC-7, Ralf Schmitt wrote: > > Johanna Belanger > writes: > > > Could anyone tell me how they got from enterprise Java to Clojure? > > Maybe the following links provide some useful information: > > http

Advice on introducing a Java dev to Clojure

Hi :) I've recently broached the subject of Clojure with another dev in my organization, and his response was basically "What's Clojure"? and I'm not sure how to answer that in a way that might inspire him. "It's a dynamically-typed functional Lisp with persistent immutable data structures tha

Re: Looking for advice to fine tune a simple function

I know. Isn't Clojure beautiful? Sigh... In the docs for *partition*, it says that partition returns a lazy sequence. And if you look at the source section of the docs for *some*

Re: Looking for advice to fine tune a simple function

You can use the *pad* argument in *partition* to add x as the value of :zone-5, like *(partition 2 2 [x] params)*. (Note you have to supply *step* if you supply *pad*.) Then you don't need the *or* or the *(last params)*. Also, like Billy did, you can use *some* instead of (*first (filter (comp

Re: Looking for advice to fine tune a simple function

Thanks for this! On Monday, February 17, 2014 4:49:38 AM UTC-8, Andy- wrote: > > On Sunday, February 16, 2014 11:19:58 PM UTC-5, Bruno Kim Medeiros Cesar > wrote: >> >> (BTW, Andy, how do you format your code so prettily?) >> > I usually just paste it into pygments.org and then paste it back into

Re: Looking for advice to fine tune a simple function

Hi, I'm fairly new to clojure as well, but I like this way, and I *think* it's idiomatic: Data structure: [{:zone-max 100 :zone-key :hr-zone-1} {:zone-max 120 :zone-key :hr-zone-2} {:zone-max 140 :zone-key :hr-zone-3} {:zone-max 160 :zone-key :hr-zone-4} {:zone-max 333 :zone-key :hr-zone-5}