'Consequential Clojure Architectures' by Janet Carr

We've all seen them. Those Clojure design decisions that come back to bite us in the ass. Our love for unopinionated software development doesn’t always pan out the way we thought, but we still like to think for ourselves when writing Clojure. So what do we do? Learn about Consequential Clojure Architectures, and build better software yourself!

Based on my experience, I'll catalog these architectures and their pitfalls for you as well as discuss potential architectures for budding codebases in Clojure(script)!

[rorycawley]

A great talk, I'd love to see a deeper talk on the applicability of the onion architecture to Clojure codebases. Thanks Janet.