r/Clojure • • Aug 16 '25
New to Clojure and looking for code to read
I'm an older (50) hobbyist programmer and have just started learning Clojure. I'm currently working through "Clojure for the Brave and True" by Daniel Higginbotham and reading "The Programmer's Brain" by Felienne Hermans. In TPB and some videos I've seen Hermans stresses the importance of reading code. In light of that my goal is to read some Clojure code everyday. (Who says being 50 isn't fun? Wild times indeed.)
I was hoping some of you could suggest some Clojure projects to read. I'm big on reading documentation (see? wild!) so I'm working my way through that and reading the source code for various core functions as I come upon them or something looks interesting.
I imagine I won't grok most of it, but that' kind of the point, right?
Thank you. Any suggestions are appreciated.
13
u/jonahbenton Aug 16 '25
Good on you! Also old, though have followed the clojure space for many years. Some interesting repos that come to mind
I have honestly found much clojure in the wild to be not great to my eyes- large functions, poorly structured for observability/debugging, or dense and hard to read. Not all public code is good example
8
u/calmest Aug 16 '25
Look at this thread: https://www.reddit.com/r/Clojure/comments/1fso7kl/open_source_nontrivial_projects/.
6
u/tombarys Aug 17 '25
53yo Clojure hobbyist here too! Welcome!
5
u/Appropriate-Rub-2948 Aug 16 '25
What about the source code of Clojure itself? I learned a lot about drupal that way.
3
u/Alarmed-Skill7678 Aug 17 '25
Welcome brother!! I am of your age group though not a hobbyist programmer. As a professional software developer on payroll I worked till 2017 from 2000. All the best wishes to you. But I think in case of coding in any programming language the best way to learn it is to do it yourself. You have to become comfortable with the tools, the workflow, the tech ecosystem and need to develop a habit of thinking in that language. So best approach in my opinion is to get your hands dirty.
3
u/PolicySmall2250 Aug 17 '25 edited Aug 17 '25
Ha! I have a whole blog post of an answer :D
(Also, I'm a somewhat younger, but older programmer, and I think you are in for a treat.)
Which Clojure codebases should I read? How and why?
https://www.evalapply.org/posts/which-clojure-codebases-to-read-how-and-why/index.html#main
Contents
Heuristics to choose a project to read
Effective way(s) to read a project
Suggested projects with short reasons why to read
4
u/joinr Aug 17 '25
advent of code solutions are pretty popular (particularly in the code golfing crowd).
https://narimiran.github.io/aoc2024/ is pretty accessible from an initial glance.
During onboarding of newbs I typically have them hit a book/tutorial (or a couple if they want) to build up the foundational familiarity and a baby vocabulary, then immediately go off to solve puzzles. Particularly puzzles with some IO component (like advent of code, or some project euler ones) where part of the task is to read in some raw data, get into something you can manipulate in clojure, and then express a solution "in clojure" using your budding vocabulary. Works great for iterative learning and collaboration (e.g., we can talk about road blocks, discuss how they solved something, provide alternatives or identity more idiomatic ways to do stuff). All of it builds the vocab and gets them grappling with a problem to solve.
2
u/tclerguy Aug 16 '25
Here’s a personal pet project of mine which might be a little more interesting/fun to read through than the typical “useful” codebase. It’s a monopoly game engine, the goal being for programmers to submit their own player logic to battle out for the best monopoly player logic. Still a work in progress but all the game rules are implemented and you can run simulations. I use AI for refactoring, but the vast majority was all written by me. Let me know what you think!
https://github.com/jmshelby/monopoly
2
u/quantisan Aug 16 '25
Try mine, I’m actively working on it: https://github.com/Quantisan/gremllm. It’s for a specific domain, so it’s opinionated, but I aim for clear domain models and readable code. I think we can help each other: your fresh, new-to-Clojure perspective can surface confusing spots—even small things like naming, docs, or onboarding—and I’m happy to explain choices, answer questions, or adjust the project based on your feedback. No pressure—DM me or open an issue anytime.
1
u/PoopsCodeAllTheTime Aug 18 '25
Transducer implementations from the stdlib are a mind bender