You probably want to watch this: vimeo.com/46163090 Also, try to think of your programs in terms of pipelines as much as possible. You get input, you produce output. That probably applies to every program ever written, but when you get how that works in Clojure, it's like an enlightment, at least it was for me. You can then structure all the processes in your program like that, and wire those up until you're done.
On Thursday, October 18, 2012 5:51:23 AM UTC+2, Brian Craft wrote: > > I'm finding the books on clojure to be very focused on low-level language > features. Are there any good references for how to design code in clojure > (or perhaps in functional languages more generally)? For example, knowing > when to use a data type or a protocol, knowing when and how to separate > purely functional code from code with side effects, making use of monads, > queues, and the other forms that one hears about in the forums, etc. -- 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
