Building a new product can be a lot of fun and you have to choose what technology stack will give you a good head start. Initially, the team chose Ruby on Rails to build a prototype which was great until our users started to grow significantly.
In this talk, I'll share our team's journey with Clojure, what worked for us and what didn't work so well.
We also tried to make Clojure more approachable, so I'll finish by sharing my thoughts on how Clojure could be advocated to appeal to the broader programming community.
YOU MAY ALSO LIKE:
- Growing a Product with Clojure: Lessons Learned (SkillsCast recorded in December 2018)
- Team Topology - Enablement mode (Online Meetup on 6th October 2022)
- LJC: Monitoring Digital Experience to Determine Feature Effectiveness (Online Meetup on 11th October 2022)
- Lightening talk: Redis Modules (SkillsCast recorded in July 2019)
- Giving my enemies a voice (SkillsCast recorded in April 2019)
Building a product with Clojure: Lessons Learned
I’m an experienced Clojure, Ruby, and Shell developer. In my professional career I have worked on client side projects (starting with old school tools like Prototype through Backbone to React), back-end applications (written in Clojure, Ruby and Go).
Most recently I’ve co-founded NomNom and work as a CTO.
I have a thing for LISPs.