The Release Train concept has been a key factor in improving developer productivity and satisfaction for the mobile team that I am in. By breaking down larger releases into smaller, more manageable/trackable chunks, we're able to avoid delays and keep things running smoothly, which helps to ensure that teams are able to deliver software efficiently and on schedule.
This is important not just for improving engineering outcomes, but also for the well-being and satisfaction of developers, as productivity and satisfaction are intricately connected. The release train concept has been particularly useful for distributed teams working on a single app, and it has been a key part of the success of these teams in recent years.
Which framework do you use for release management in your team? Please let me know via Twitter, Linkedin, or email.
Now, onto the ninth week’s episode.
It seems that Facebook's implementation of a quasi-continuous delivery system in 2017 has allowed the company to rapidly and safely release updates and new features to its users.
🔗 https://engineering.fb.com/2017/08/31/web/rapid-release-at-massive-scale/
Rushing can lead to mistakes and slower progress overall. It is important to follow a process and make steady progress toward the goal.
🔗 https://medium.com/codex/boring-is-beautiful-in-software-development-2067f6a54ea7
Like many of us, the mobile developer experience team at Slack aims to empower developers to confidently ship code and have a positive and productive experience. They implemented an automated flaky test suppression system to address the high rate of test failures caused by flaky tests.
🔗 https://slack.engineering/handling-flaky-tests-at-scale-auto-detection-suppression/
No posts

Comments
Nothing yet. Say the first thing.
Sign in to join the conversation.