Clojure in Product. Would you do it again?
Clojure in Product. Would you do it again?
Podcast Description
Real-life product stories and insights from top Clojure leaders.We launched this podcast because we're fascinated by a paradox: Clojure is an exceptional language with a powerful philosophy behind it, yet it remains relatively niche in the industry. By talking to teams who've actually implemented Clojure in production, we're trying to understand this disconnect.Is there something fundamental limiting Clojure's adoption, or is it just circumstantial?Through conversations with people, who've taken the leap and built real systems with Clojure, we're exploring whether they would "do it again" — and more importantly, why or why not. We're hoping these real-world stories can help understand Clojure's place in the industry and perhaps shed light on its future potential.Visit our podcast page: freshcodeit.com/podcast
Podcast Insights
Content Themes
Focuses on the adoption and implementation of Clojure in production environments, discussing its benefits and challenges. Specific themes include software development processes, hiring practices, and team culture, with episodes like 'You need boundaries to do a meaningful work' and 'ClojureScript is a Clojure killer app' providing tangible insights for software teams.
Real-life product stories and insights from top Clojure leaders.
We launched this podcast because we’re fascinated by a paradox: Clojure is an exceptional language with a powerful philosophy behind it, yet it remains relatively niche in the industry. By talking to teams who’ve actually implemented Clojure in production, we’re trying to understand this disconnect.
Is there something fundamental limiting Clojure’s adoption, or is it just circumstantial?
Through conversations with people, who’ve taken the leap and built real systems with Clojure, we’re exploring whether they would “do it again” — and more importantly, why or why not.
We’re hoping these real-world stories can help understand Clojure’s place in the industry and perhaps shed light on its future potential.
Visit our podcast page: freshcodeit.com/podcast
Welcome to the 10th episode of our podcast, “Clojure in product. Would you do it again?”, where Artem Barmin and Vadym Kostiuk speak with Cam Saul, Chief Architect at Metabase, an open-source business intelligence platform. In his role, Cam wears multiple hats, including reviewing architectural documents, managing developer tasks, and writing custom linters to ensure code quality.
We discuss the integral role of Clojure in Metabase’s development and how transitioning from Python allowed the team to ship features much faster. Cam also shares insights into the blend of Clojure and JavaScript developers, highlighting the advantages of Clojure’s stability, which enables the team to build upon existing work without the frequent changes seen in other programming environments.
The open-source foundation of Metabase has fostered a collaborative culture that attracts external contributors, some of whom joined the team after submitting valuable requests. Cam reflects on the journey of hiring Clojure developers, emphasizing the learning opportunities it provides. We conclude with Cam’s thoughts on the Clojure community and his response to a question from our previous guest, Alexander Johannes from JustOn.
Worth your attention:
- Fast in-product analytics: metabase.com
- Freshcode Clojure Team: freshcodeit.com/services/clojure-development-company
Disclaimer
This podcast’s information is provided for general reference and was obtained from publicly accessible sources. The Podcast Collaborative neither produces nor verifies the content, accuracy, or suitability of this podcast. Views and opinions belong solely to the podcast creators and guests.
For a complete disclaimer, please see our Full Disclaimer on the archive page. The Podcast Collaborative bears no responsibility for the podcast’s themes, language, or overall content. Listener discretion is advised. Read our Terms of Use and Privacy Policy for more details.