Memory leaks are a common problem when writing iOS applications, and while we all know we should be on the lookout for them, it’s often too easy to miss a vital weak reference. By leveraging integration testing, we can catch these issues and spend more time actually building features.
Backstage Blog RSS
January 3rd, 2019 iOS Swift Testing Integration Testing for Memory Leaks By Matthew Healy
November 23rd, 2018 Engineering Culture, Tech Debt A Pragmatic Approach to Tech Debt Reduction By Christine Patton
Almost every company accumulates tech debt as time goes on. Tight deadlines, changing requirements, scaling issues, poor or short-sighted system designs, knowledge silos, inconsistent coding practices, turnover of key staff — these things all happen and can contribute to tech debt. So what can be done about it once it’s there?
November 6th, 2018 Engineering iOS Architecture How We Develop New Features Using Offsites and Clean Architecture By Guilherme Endres
In 2017, our team of six engineers wanted to try out a clean architectural pattern and decided to use VIPER. In the text below, I’ll cover how the team worked on this.
September 18th, 2018 Engineering Microservices Using Kubernetes Pod Metadata to Improve Zipkin Traces By Steve Conover
We revisited our distributed tracing setup and incorporated Kubernetes pod metadata into it, significantly enhancing our engineers’ ability to troubleshoot problems that cut across microservices.
August 31st, 2018 Engineering Monitoring Testing Hands-Off Deployment with Canary By Jorge Creixell and Tobias Schmidt
At SoundCloud, we follow best practices around continuous delivery, i.e. deploying small incremental changes often (many times a day). In order to improve the user experience, we’ve been exploring different ways of reducing the impact and the Mean Time to Recovery (MTTR) of faulty deployments. Enter canary releases.