Freshcode

09/04/2026

🧡 Freshcode is proud to sponsor and partner with Dutch Clojure Days 2026!

Join us on Saturday, May 9, in the beautiful City of Wesopa (Weesp, Amsterdam).

Oleksandr Slobozhan and Vadym Kostiuk will be at our table — drop by to talk Clojure, product engineering, or your next project.

See you in Weesp!

10/02/2026

🚀 Artem Barmin just wrote a new piece on why legacy e‑commerce stacks buckle under modern scale.

He tells how functional languages like Elixir and Clojure help migrate safely, cut costs, and keep teams lean.

Read it the Destination CRM:

Functional programming with languages like Elixir and Clojure transforms e-commerce scaling from a costly infrastructure problem into a disciplined, modular challenge that businesses can solve with smaller teams and less rewriting.

03/02/2026

🎧 New episode of "Clojure in product. Would you do it again?" is out — this one’s about running hashtag 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:
🔥 What being a “Clojure island” actually means for integrations and tooling
🔥 How security audits and dependency scans steer engineering choices
🔥 Keeping a 9‑year‑old codebase simple, sharing knowledge, and bringing new Clojure folks up to speed
🔥 When Clojure makes sense — and when it’s more complicated than that

Have a look at using a non‑standard stack at scale: https://www.freshcodeit.com/podcast/it-allows-a-small-team-to-achieve-really-great-goals

16/01/2026

💥 Heads up — Freshcode CTO Artem Barmin just published a sharp, no‑nonsense guide on DevOps.com: “(Almost) Seven Signs That Your JavaScript Project Is Legacy.”
If you’ve ever opened a repo and felt time travel creep in, Artem’s checklist (deps, callbacks, build‑systems, jQuery, missing tests — you know the hits) is an easy read and a great cheat‑sheet for next steps.
Read it here: https://devops.com/almost-seven-signs-that-your-javascript-project-is-legacy/ — and tell us: what was the one clue that made you know a codebase needed a rescue?

Learn how to identify legacy JavaScript projects by examining outdated practices, architectural choices, and testing strategies.

09/01/2026

🎧 Missed "Clojure in product. Would you do it again?" latest episode? Catch how Jeremiah Via explains why NYT’s search has run on Clojure for nearly a decade.
Listen here: https://www.freshcodeit.com/podcast/clojure-still-gives-the-biggest-performance-boost

05/01/2026

💖 As we kick off 2026, we’re carrying the warmth of last year’s meetups — from cafés to offices across different cities.

Thanks to the Freshcoders for the ideas, support, and camaraderie.

Wishing everyone a year of meaningful connections, joyful moments, and bold achievements!

01/01/2026

З Новим роком!

28/11/2025

💥 Thrilled to share our new 11th "Clojure in product. Would you do it again?" episode with Jeremiah Via from The New York Times.

⚡ We cover how Clojure quietly powers NYT search – concise code, JVM interop, REPL‑driven workflow. It scales for heavy Kafka ingestion and keeps teams stable. Jeremiah explains onboarding – AI cuts the friction – and calls for better NLP/vector tooling.

👉 If you care about resilient, developer-friendly backends, give it a listen: https://www.freshcodeit.com/podcast/clojure-still-gives-the-biggest-performance-boost

13/11/2025

🎯 Today we're thinking about the gap between "technically correct" and "actually usable."
That button that's too small. The flow that takes 6 clicks instead of 2. The error message that says nothing.
Small details. Big difference.
At Freshcode, we obsess over this. Because shipping code isn't shipping value, shipping usable code is.
If your product feels clunky, it's not broken – it's not being tested with real people.
Go make something people actually want to use.