Clojure in Product. Would you do it again? Episode 2. We choose the best tool for the job, with Adam Tornhill, CodeScene
10 snips
Dec 3, 2024 
Adam Tornhill, founder of CodeScene and author of "Your Code as a Crime Scene," dives into the world of Clojure and software development. He shares his team's journey adopting Clojure, discussing challenges like performance and investor perceptions. Tornhill emphasizes the importance of technical decision-making and managing technical debt. He also explores the role of AI in coding and the value of documentation. Plus, he touches on onboarding challenges for newcomers to Clojure, advocating for better mentorship in the programming community.
AI Snips
Chapters
Books
Transcript
Episode notes
Why Clojure for CodeScene?
- Adam Tornhill chose Clojure for CodeScene due to its JVM integration and perceived productivity boost.
- He also valued the enjoyment of coding in Clojure, anticipating long hours working on the project.
Addressing Initial Concerns
- Initial concerns about Clojure's performance and hiring developers proved unfounded.
- Investors questioned the choice, suggesting Java for easier hiring.
Clojure's Performance and Hiring
- Clojure's performance exceeded expectations, requiring only one rewrite in 10 years.
- Hiring skilled, passionate Clojure developers proved easier than anticipated.
