Supporting the Product through Continuous Delivery
summary
Dashlane describes concrete continuous delivery practices: a multi-year investment (2–3 years) across eight platforms (iOS, Android, Mac, Windows, Chrome) with CI, mandatory code review and a layered test pyramid plus daily monitoring. They build an internal feature flipping system and an embedded A/B test engine, and use progressive rollout (example: 1% rollout catches a production certificate crash, preventing support exposure). Warnings: remove flag dead code, don’t use flags as config, synchronize marketing/product/engineering before promotional launches.
AI-written summary · about
chapters (13)
- 0:00Intro
- 2:07Prerequisites for Continuous Delivery
- 4:26Test Automation
- 6:20Continuous Operation
- 8:30Progressive rollout
- 9:51Feature flipping
- 10:54Future flipping
- 11:24Warning about Future flipping
- 11:56AB Test Engine
- 13:12Communication Failure
- 17:30Investment to Continuous Delivery
- 18:05Continuous Delivery Practices
- 19:15Communication
related talks
33mContinuous Delivery - What does good really look like?
46mContinuous Delivery for Native Apps
45mTurning continuous delivery into competitive business advantage
55mContinuously Delivering Continuous Delivery
06mDeploying rapidly for continuous integration
28mMinimum Viable Continuous Delivery
29mBanking on Continuous Delivery
41mImplementing Continuous Delivery with IOS