"We were tired of silly runtime exceptions breaking our souls."
That's how Mike Onslow responded when we asked him why he made the decision to start using Elm at Clarity Voice. He was a software developer facing the need to replace a 10-year-old internal system that was showing signs of its age. And Mike was tired of working with a broken soul.
But you won't sense any exhaustion in Mike these days. He is cheerful, optimistic, and brimming with creative ideas. This spring they're excited to kick off a project rebuilding the frontend of their ERP system.
So how did they go from crushed souls to happy coders? What was Mike's simple, yet brilliant, strategy for introducing Elm? And how did he "sell" Elm to his management such that it's now the language of choice at Clarity Voice?
It's a great story and we're pleased that Mike and Clarity Voice have given us this opportunity to share it with you.
Their library worked well… for a while. But then their requirements grew and they needed to deal with more complex workflows. As they began to layer in more state changes and dependencies, two things happened at the same time: their app got more difficult to develop and less reliable....