Working with sharp tools - A case study of Continuous deployment
summary
A production app used in 22 countries and translated into 24 languages replaces rigid spec documents with a shared Trello backlog where clients prioritize issues. String edits flow from POEditor into GitHub via webhooks, Bitrise runs tagged builds, Hockey distributes signed enterprise builds, and Slack channels carry build IDs and crash reports so deploys, regressions and priorities are discussed against the exact commit. The pipeline shortens feedback loops, surfaces technical debt, and lets teams push iterative builds to clients fast.
AI-written summary · about
chapters (6)
- 0:00Introduction to talk
- 1:50Moving away from detailed requirements
- 4:23Continuous integration workflow explained
- 7:24Automated builds and client communication
- 9:12Benefits of transparency and collaboration
- 10:37Call to action and conclusion
related talks
58mWorking with sharp tools — continuous integration and deployment as a way to reduce friction
34mEnabling a Continuous Deployment Mindset
01h 01mA team's transition to Continuous Delivery
47mContinuous Delivery Warstories
46mThe Software Factory
42mA Modern Development Culture for a Modern Development Process.
33mSoftware development practices for companies that want to make an impact
27mTaming the Kraken - How Operations enables developer productivity