After exploring why frameworks and why not frameworks, I dive into the design priorities I think a web framework should have.
We explore three arguments against frameworks, address them, then turn them into challenges to be overcome.
While contemplating a Clojure web framework, I explore the reasons we use web frameworks in general. I conclude that the framework should support a learnable development process.
Poor open-source development practices, neglect for the beginner experience, and lack of communication have come up as complaints against how Cognitect stewards Clojure. I address the complaints with a plea that we do more as a community.
I was on the Defn Podcast. We talked about Clojure, testing, and PHP :) Here is a transcript.
My third rehearsal for my upcoming Clojure/conj talk.
My upcoming Clojure/conj talk is fast approaching. I recorded two rehearsals in two days. Watch them!
We organized a Clojure workshop. Here's what went right and what we should do next time.
Concurrency and parallelism are concepts that we make use of every day off of the computer. I give some real world examples and we analyze them for concurrency and parallelism.
You actually need to learn nothing. But it's more complicated than that. This article will show you what can set you apart.