Reducing technical debt at Moonpig

Dealing with technical debt before it kills your company growth

If you started your software business before agile practices were widespread, chances are you may now be dealing with the pain of technical debt. Legacy code, lack of automated test coverage, painful deployments, limited logging… sound familiar?

When Moonpig reached the ripe old age of 14, the cost of technical debt was beginning to severely impact the ability of the business to grow. It was time for a change. Technical debt is notoriously difficult to quantify, and thus it’s very hard to secure time and investment to deal with it.

We have managed to change — don’t get me wrong, we’re not perfect. You won’t clean up 14 years of poor code in 3 years, but we’re in a better place and we’re getting better all the time. Crucially, we’ve reduced our deployment cycle from once every 3 weeks to 3–4 times a day.

Read the story of how we made the case for technical debt, and having secured the time, how we set about using it constructively.

Like what you read? Give Amanda Colpoys a round of applause.

From a quick cheer to a standing ovation, clap to show how much you enjoyed this story.