Clojure in Product. Would you do it again? Episode 9. You need boundaries to do a meaningful work, with Alexander Johannes, JustOn
Feb 10, 2025
Alexander Johannes, Head of Development at JustOn, shares his insights on integrating Clojure into fintech development. He reflects on his journey transitioning from Salesforce to Clojure, emphasizing the capabilities it brings for rapid and meaningful solutions. The conversation dives into the challenges of team dynamics, hiring niche candidates, and maintaining a strong culture with local talent. They also explore coding pitfalls in Clojure and best practices for functional programming, highlighting the balance between delivering timely features and ensuring code quality.
AI Snips
Chapters
Transcript
Episode notes
Clojure's Hobbyist Origins at JustOn
- Clojure was introduced to JustOn initially through a hobbyist project focused on creating mock-up classes for testing the Salesforce platform Apex code.
- This small project served as the seed for integrating Clojure fully into their tech stack.
Evaluate Languages with Challenges
- Conduct programming challenges using different languages to evaluate fit for your project requirements and developer happiness.
- Factor in existing expertise and ecosystem integration when choosing a tech stack like Clojure on the JVM.
Boundaries Foster Creativity
- Having no boundaries in technology can be stressful, as constraints guide creativity and meaningful work.
- Deciding on architecture means killing many options, raising concern if the right choices were made.