A web search turned up the following:

http://stackoverflow.com/questions/3628958/good-clojure-code-examples

https://groups.google.com/forum/#!topic/clojure/U6fLpc_NO98

I have heard from more than one source that the clojure.core source code is 
good to read. Maybe I'll get around to it myself someday. Good luck, and 
keep at it!

--Gregg

On Tuesday, May 27, 2014 6:54:02 PM UTC-7, Randy Chiu wrote:
>
> Hi Gregg,
> Your suggestion is very good and explicit,thanks for your response.
> I'd like to ask you another question since you mentioned :
> >>> spend *a lot* of time studying other people's solutions, looking at 
> both the factors of elegance and readability in solutions. 
> do you have any good projects/solutions recommended?
>
> 在 2014年5月28日星期三UTC+8上午3时15分37秒,Gregg Williams写道:
>>
>> Hi, Randy,
>>
>> I'm several years into learning Clojure. Here's what has worked for me:
>>
>> * Use either Light Table or (if you're determined) Emacs as your IDE.
>> * I learned a lot from taking this free online course: 
>> http://iloveponies.github.io/120-hour-epic-sax-marathon/index.html
>> * I have *all* the published Clojure books. To start, I recommend 
>> Programming Clojure, 2nd Ed. (Halloway), or Clojure Programming (Emerick 
>> et. al.).
>> * Start on the exercises at 4clojure.com (sorted from easiest to 
>> hardest) ***AND*** (this is where you will learn the most) once you've 
>> completed an exercise, spend *a lot* of time studying other people's 
>> solutions, looking at both the factors of elegance and readability in 
>> solutions. If you can't figure one out, keep at it until you do.
>> * Ask for help on stackoverflow.com. You get better results there 
>> because people have an incentive to write clearly.
>> * In your own code, prefer readability over brevity (this bucks the 
>> common wisdom of the community). Use multiline functions that show 
>> structure through (auto)indentation. Symbol names are tricky--too short and 
>> they're cryptic, too long and they hide the code; find what works for you.
>> * Watch videos from the various Clojure conferences and groups, 
>> especially those from Rich Hickey and the most visible contributors of the 
>> Clojure community. Their talks have given me a lot more about the 
>> philosophy of Clojure and how to think about coding in Clojure than most of 
>> the printed books.
>> * Finally, here are my Clojure bookmarks, which go back almost five years 
>> https://www.pinboard.in/search/u:GreggInCA?query=clojure. Older links 
>> are, in some cases, outdated. Use your best judgement.
>> * Persevere. Clojure is not an easy language/environment, but it is 
>> uniquely oriented to future hardware and it is very powerful.
>>
>>
>>
>> On Tuesday, May 27, 2014 4:58:44 AM UTC-7, Randy Chiu wrote:
>>>
>>> Hi all,
>>> I'm new to clojure and want to find some suggestion for learning 
>>> clojure. I googled some project about "how to learn clojure" but without 
>>> any perfect answers until now.
>>> I worked on linux kernel in last several years mainly with C, and I'm 
>>> recently interested in lisp. I try to read some books about common lisp and 
>>> scheme  and even clojure, so I think I know a little about lisp but lacking 
>>> for practice. 
>>> So, I'd like to know any project I could read(or even try to join in), 
>>> or any other suggestion for learning this new lisp dialect please let me 
>>> know.
>>> Thanks for your advance.
>>>
>>

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