I spend a lot of time reading Clojure code and running it in my head. I realise a lot of folks are very happy to test things out in the REPL, and so am I, of course, but I'm getting a lot of mileage out of my understanding of the wonderfully succinct Clojure core and just reading. Especially when the code is part of a bigger flow that would be annoying to set up in the REPL, but also when reading code outside of an editor environment, like on Github. And I'm pretty sure that said succinctness of the Clojure core is to praise for my ability to do this 🙌 Thanks again, @richhickey and everyone involved! 😄 Being able to work with Clojure adds joy to my programming job every day.
100% agree with this. Before Clojure I worked in C# and reading code was such a slog. huge project overhead, tons of indirection with interface files, so many constructuors, dependency injection, that finding wherre the actual work happened was a huge chore. Reading Clojure code is an absolute delight
Today's gratitude goes to @jeroenvandijk for a small PR against my Polylith external test runner to support randomization of test namespace order during project testing. I get a little thrill each time I watch the test suite running, seeing nses load and get tested in a different order each time, increasing my confident that I have no state-related bugs lurking anywhere! Thank you!