This isn't in the same league as any of those books, or the anything 
recommended by anyone else. And you probably already know everything it has 
to teach. But it seems worth mentioning.

I threw this together a couple of years ago:

https://github.com/jimrthy/clojure-introduction

It's really meant to be something you open in your editor and then used 
with its REPL integration to get a feel for the high-level overview.

If you don't have an editor set up with REPL integration, stop everything 
else and get that working. That's one of the major advantages that lisps 
have over almost any other language. If you try to approach this the way 
you'd write code in, say, python or java, you're going to be sad.

On Wednesday, December 6, 2017 at 5:24:22 PM UTC-6, Clojure beginner wrote:
>
> Hi all 
> I heard about Clojure a week ago and have a new assignment at work to 
> learn, develope and deploy to production. I haven't developed in 2 years. 
> Programming background is: mainframe and informatica. I have bought 5 
> books: and Clojure programming, Clojure for brave and true, Clojure in 
> action, programming Clojure, the joy of clojure. I have also been on the 
> main Clojure website. It's been a week and I still don't understand the 
> meat and potatoes. Any recommendations where I can get a walk through of it 
> with real examples. 

-- 
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.

Reply via email to