Clojurians Log v2
clojuredesign-podcast
Have you joined a project and felt frustrated with the docs or tests? Was it hard to figure out the structure and flow? Worse yet, it's your old code! Listen to our new series about setting your future self up for success! https://clojuredesign.club/episode/114-brand-new-again/
What's the first thing you do when you start working with an existing project?
Exciting! I wonder if this touches a bit on one of the reasons I've heard people lament the lack of a Clojure web framework: known structure. If every project is this bespoke unicorn, you're always going to spend a bunch of time just trying to build yourself a map of the terrain, rather than being like, okay, I know the shape let me just go poke in here to understand the domain model or there to understand the routes
Yes, there are definitely less guiderails for organizing your project in Clojure. I do see the appeal of having a "higher authority" of a framework to settle disputes about structure too. What I don't like about frameworks is the learning curve, and the tendency for the framework itself to accrete lots of complexity. In this series, I hope we can clearly elucidate the working principles that we use for our own projects. As a consultant for hire, I end up walking into my old codebases quite a lot over time, so I definitely optimize for getting up to speed quickly again.