At the time, I’d never coded in Clojure, nor had anyone else on the early engineering team. We weren’t able to rely on historical experience to guide the decision, because none of us had built something comparable. But everyone had experienced accidental complexity, and the alignment with our problem space and strategic principles was excellent. We took the leap and have never regretted it.
Clojure , on the other hand, has simple constructs that allow us to focus on the problem we are solving, making evolving the system a small incremental challenge, which doesn’t get that much harder over time.
Every entry is a verbatim quote and a link to the public post it came from. Nothing is paraphrased. If it is not on record somewhere public, it is not here.
The verdict is what they actually said: loved and liked are explicit; recommended means they told others to get it; uses means they only say they use it; read is a book on their public shelf with no verdict; mixed and disliked are kept too.
A dashed affiliate link, sponsored or their own label means the post disclosed a relationship. It is shown, never hidden.
The small bar beside a date shows how dated a recommendation is for its kind of thing.
The bar shows how dated a recommendation is, for its kind of thing. Full and green is recent. It drains, and turns amber and then grey, as the post gets older.
What counts as old depends on the thing. A laptop praised four years ago has been replaced twice; a book loved twenty years ago is probably still loved. The bar is empty after about:
Hardware, services4 years
Software5 years
Podcasts, courses, other8 years
Books25 years
A striped bar means the post carries no date and the date shown is an estimate. No date at all, no bar.