The General Development Flow at Ozon: How to Make Developers' Lives Easier
summary
Describes how Ozon redesigned its development workflow to make engineers’ lives easier, explaining the problems developers faced previously and the motivations for change. Covers the project’s starting point and the resulting architectural organization of the common development flow, including how components and processes are arranged inside that architecture.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 2:55Team history
- 5:45Why unify the Flow
- 7:53Feature development stages
- 8:15Dev environment setup
- 12:54GitLab automation
- 15:44Release branch testing
- 18:36Production deployment prep
- 20:25Ozon deployment strategies
- 22:56General Flow diagram
- 25:01Fix Flow for urgent fixes
- 25:45Automation system architecture
- 31:25Summary and metrics
- 33:56Q&A
related talks
26mArchitecting A Great Developer Experience
45mDeveloper Joy – How great teams get s%*t done
47mTransforming Developer Experience: A Tale of Recovery & Innovation
27mRethinking Developer Experience
24mDevEx on Steroids: 🚀 5 Hacks to SUPERCHARGE Developer Experience
45mUnlocking High Performing Teams with Open Source
43mThis Is a Requirement. — "And what does it do?" — "It lights up blue!"
41mHow UX Saved My DevOps
