"Clojure in product. Would you do it again?" podcast new episodes

What happens when a compact engineering team must keep search humming for millions? Episode 11 of “Clojure in product. Would you do it again?” with Jeremiah Via (The New York Times) tells that story.

We unpack why Clojure fits: terse, JVM-friendly services, REPL-first development, and a Kafka→Clojure→Elasticsearch pipeline tuned for bursts. Jeremiah also shares practical onboarding tips (AI is lowering the ramp) and flags a clear gap – better native NLP/vector tools in the ecosystem.

Curious about resilient, developer‑centric backends? Give it a listen: Even in the AI era, Clojure gives the biggest performance boost, with Jeremiah Via, NYT - Freshcode

:headphone: New episode of “Clojure in product. Would you do it again?” is out — this one’s about running Clojure inside a big global firm.
We sat down with Marcin Maicki (Global Data Developer & Lead Developer at Dentons) to hear what it’s like keeping a Clojure system running in a C#/TypeScript world. We talked about real, everyday stuff like:
:fire: What being a “Clojure island” actually means for integrations and tooling
:fire: How security audits and dependency scans steer engineering choices
:fire: Keeping a 9‑year‑old codebase simple, sharing knowledge, and bringing new Clojure folks up to speed
:fire: When Clojure makes sense — and when it’s more complicated than that

Have a look at using a non‑standard stack at scale: It allows a small team to achieve really great goals, with Marcin Maicki, Dentons - Freshcode