Jarrod, The book Clojure Programming<http://www.amazon.com/Clojure-Programming-Chas-Emerick-ebook/dp/B007Q4T040>has a chapter (19) dedicated to your very question. I think the most important piece of advice is "Be Prudent" by choosing where Clojure fits and by starting slow. Try to find small self-contained problems and solve them. This will demonstrate the language's usefulness far better than any logical argument could.
On Tuesday, March 11, 2014 3:31:43 PM UTC-6, Jarrod Swart wrote: > > Gary, > > Thanks for your observations. I agree it doesn't necessarily have to be > all or nothing. I'm hoping to get as much as possible insight before I > present to the founders. > -- 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/d/optout.
