Onzo operate an energy analytics platform. This allows utilities to make the most of their customer data.
The tech stack
- Akka, Akka persistence
- Apache Spark & Kafka
- Google Tensorflow, Python Scikit-learn
On the technical side we essentially had two teams; an engineering team, and a data science team.
As the sole technical architect I was ultimately responsible for the production platform.
What did I learn
When the direction of the business is unclear it’s best to get something up and running quickly. We need to accept
that software developed this way will have to be rewritten at a later date. This is usually a hard sell to CFOs and
investors. However, there is tremendous value in writing “throw away” code. The business can validate which
ideas are actually viable. The tech teams can discover the challenges and pitfalls of a particular domain at relatively
It’s not the first time I’ve discovered this principle. Over the years, I’ve worked on many software projects,
I would have to admit that we rarely get it right first time. My time at Onzo really reinforced this belief.