Software development practices for companies that want to make an impact
summary
Argues that an online product must push small changes to production constantly and shows how: continuous deployment on Kanban plus a CI/CD pipeline, end-to-end test automation (unit, system, visual) and post-deploy sanity tests, single branch per component with feature bits for per-client canaries, and infrastructure as code. Reports thousands of deployments per month and says this setup raises quality, speeds delivery, enables shared ownership of code and ops, and scales without repeat outages.
AI-written summary · about
chapters (7)
- 0:00Introduction and context
- 1:25About the speaker and Innovid
- 4:17Continuous deployment practices
- 10:38No code ownership explained
- 17:46Rallying around business goals
- 22:02Implementing changes gradually
- 23:32Q&A session
