DevOps 2.0 - Bigger, Badder with More Automation
summary
Data shows pull requests sit idle about 50% of the time and a third idle for 80% of their lifespan, creating long context switches and risk. A measurable intervention—displaying an estimated review time—cuts pickup from hours to minutes. Practical fixes include a ship show ask classification, rule files stored in-repo (runs via GitHub Actions) and automated flows like LinearB’s git stream that auto-label, summon security reviewers for gateway changes, and auto-approve trivial CSS edits.
AI-written summary · about
chapters (18)
- 0:00Intro
- 0:43History of Software Development
- 2:37CICD
- 4:12Feedback
- 6:52Pull Requests
- 7:17Idle PRs
- 8:16Context switching
- 8:45Whats missing
- 12:43How context influences reviewers
- 14:19Ship Show Ask
- 18:27Context
- 20:03Review
- 24:05Measurements
- 24:30Advanced Considerations
- 28:10GitHub Actions
- 29:40Continuous Merge
- 30:17Linear B
- 30:55Git Stream
related talks
43mDevOps 2.0 - Bigger, Badder with More Automation
55mDevOps isn't just about developing
25mSpace-Age GitOps: The Rise of the Humble Pull Request
28mPull Requests: Merging good practices into your project
47mHow to Optimize Non-Coding Time
26mA State of Continuous Merge: The Secret to More Productive Dev Teams
38mHow to Optimize Non-Coding Time
17m50 shades of PR