We explore when it is safe to extract out an abstraction and when you need to go deeper and rebuild it from scratch.
We explore some of the background behind the meaning of the word abstraction and why we do it.
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.
One of the great things about very robust and powerful abstractions is that they can give you tremendous leverage. The leverage can be so great that you can build something much greater than the sum of its parts. However, I worry that the web is an end to this kind of abstraction. I'd like to explore why that is and what we can do about it.
How a programming language can be an idea.
My third rehearsal for my upcoming Clojure/conj talk.