The Blog

Hello there! We'd love to help you learn how we run effective postmortems at Cleo. Interested? Let's get to it.

Cassie, Technical Lead, explains how we approach production incidents and outlines our on-call process for Engineering.

Collaborate. Innovate. Create. Fell explains our approach to innovation at Cleo.

Josh, Tech Lead, dives into what he looks for when reviewing pull requests at Cleo. If you're looking to write code that scales better, this is a must read.

Our Engineers share their favourite talks and memorable moments from Brighton Ruby Conference 2022.

At Cleo we think that the deliberate, conscious and careful accumulation of tech debt is a powerful tool that lets us ship code and value to our users faster. Fell explains how we manage our technical debt.

Josh, Tech Lead at Cleo, outlines our approach to migrating our primary key columns from integer to bigint.

Fell, Tech Lead at Cleo, shares his techniques for effective problem solving.

We built a new tool called re_dms in order to allow streaming replication of data from postgres to redshift. Here, we’ll outline why we needed this new tool, our technical considerations,and some challenges we overcame.

Last year, our Heroku Postgres database was fast approaching its 3TB storage limit, the maximum size that Heroku supports at time of writing. To make sure our community of 4 million people could continue to work on their financial health with Cleo, it was essential to migrate away from Heroku as quickly and smoothly as possible.

You didn’t hear it from me, but Cleo Engineers aren’t perfect. We have bugs. We have quite a few of them. Our relentless focus at Cleo is to make it as simple and joyful as possible for our users to level up their relationship with money.

The ineffable cool that is Cleo Designer, Corinne Hitching, needs no introduction. Designers, or anyone who’s reading, please enjoy this exploration with one of our original Cleo designers.