Archive

I'm sure for some of you Model-View-Controller (MVC) resembles more of an anti-pattern than something to reach for when writing Clojure, but I think it's a great example of what architecture should accomplish, especially what can be accomplished in Clojure. MVC decouples state, state changes, and state usage. One way

One day my squad mate at a Clojure startup committed a macro to the codebase, and I was quick to reprimand them for it as the same functionality could have been implemented with Clojure core functions. Peeling back the decision rationale, I discovered my colleague had never learned the first

we can ship production code with Clojure. A strange bit of grumbling I hear from developers directs their angst toward not having "compile time type checking errors"

This post is the second in a series. You can find the first post in the series here where I covered Null Object, Singleton, Command, Observer, State, Visitor, and Iterator. Patterns * Preamble * Builder * Chain of Responsibility * Proxy * Adapter * Template Method * Flyweight * Strategy Our story continues Edmund, a bright, awkward young

Clojure either directly supports, or easily supports the use of common design patterns like singleton, command, observer, visitor

I think there's another reason this problem persists in Clojure. There's no Rails for Clojure.

Turns out, it's a yak barbershop.