Tell me if this story sounds familiar. At your company, there is The Tool. Everyone is required to use The Tool. It is the central information hub for the entire company. Or at least it was supposed to be. In practice, it is where information goes to die.
After installing the latest *env utility, I decided to stop and count how many of these things have accumulated in my shell.
Inspired by a recent article comparing the number of system calls at start made by various compilers, I decided to do the same with my Clojure start-time experiments.
I’ve heard the phrase “where information / knowledge goes to die” applied to a variety of targets: email, wikis, various software products, even governments. But I wasn’t sure where it originated.
On the impossibility of separating content from presentation I like writing in Emacs’ Org mode, not because it’s an especially good means of writing prose, but because I already use Org so heavily for notes and source code. My last post was written in Org mode. But my blog remains, as it always has been,… Continue reading Org Mode for Blogging
From 2011 to 2015, I wrote an annual Clojure Year in Review post, attempting to summarize all the interesting things that happened in Clojure in the last year. After 2015, I gave up. There was just too much happening, and I couldn’t keep track of it all. A couple of years ago, I got tired… Continue reading Clojure Start Time in 2019
In case you didn’t know, I started a podcast this year: No Manifestos. One of the interesting things about podcasting is that it’s difficult to know who’s listening. This has even been suggested as the reason for the genre’s success, as it prevents the aggressive tracking and reductionist analytics that have made such a cesspool… Continue reading Old Fashioned Web Analytics in a Newfangled Serverless World
The inimitable Chouser has written an exhaustive analysis of the many ways to flatten a sequence of sequences in Clojure.
Continuing my series of Clojure do’s and don’ts — which, as always, is a mix of technical recommendations and my personal stylistic preferences — and continuing on the topic of the previous post in this series, here are some more arbitrary rules about anonymous functions.
A mistake that shows up at least once in almost every class I teach. The Clojure reader macro #() creates an anonymous function whose body is a single expression, and that expression must be a list.