Β« Oatmeal

Tagged "clojure"

Follow this tag

In reply to: Key Lesson: Building CloudRepo With Clojure

In Clojure, if you adopt the β€˜Data is the API’ paradigm then designing systems is primarily about identifying your data and how it flows through your functions. Data can be represented by a small set of abstractions, in particular a map, and so would reduce the requirement to write the glue code that is so commonplace in Java (a.setFoo(b.getFoo) , etc.).

Also, if functional programming is your jam, don’t miss this article’s use of Data Flow diagrams to describe Clojure code πŸ’―

While reading Clojure for the Brave and True, I’ve also been working my way through the lisp koans. At this point I’m pretty obsessed with lisps, and am growing increasingly excited to use one for a project. Generally speaking, I feel most cozy working with a really small (some would say β€œconstrained?”) toolset. Lisps most totes fulfill this coziness.