Clojure in Product. Would you do it again? Episode 1. Now we are writing in Clojure, with Kalle Korhonen, Quuppa
Nov 27, 2024
Kalle Korhonen, CPO at Quuppa, brings his expertise to the discussion on integrating Clojure into a Java-based system. He shares insights on the challenges and triumphs of transitioning to Clojure and ClojureScript, touching on architecture, team collaboration, and the adoption of domain-specific languages. Kalle also delves into the unique recruitment dynamics for Clojure projects, emphasizing the value of familiarity with Clojure libraries. The conversation wraps up with thoughts on AI's future role in programming, focusing on the necessity of contextual input.
AI Snips
Chapters
Transcript
Episode notes
Clojure Binding and Community
- Quuppa developers chose Clojure for passion and practicality; switching languages mid-project is not viable.
- Experienced Clojure devs feel spoiled by the language's consistency and power compared to others.
Centralized Tech Decisions Work
- Technical decisions at Quuppa are agile and centralized, not democratic or committee-based.
- Smaller teams enable quicker adoption of new technologies without bureaucratic hurdles.
Beware Overengineering and Microservices
- Overengineering can harm software projects, especially when blindly adopting microservices or building unnecessary DSLs.
- The variety of small Clojure libraries is a strength compared to heavy monolithic Java frameworks.