DevOps isn't just about developing
summary
Argues developers now spend 75% non-coding time on reviews, docs, meetings and security, cites 37% of work wasted by poor collaboration and ~23 minutes lost per tool switch. Shows concrete GitHub features used to fix this: repo team management, issues/projects/discussions, global search, a multilingual dietary-requirements app built with community contributors, and engineering fixes like merge queue to avoid repeated CI runs and Copilot PR summaries (Enterprise) to fill missing pull-request descriptions. Demonstrations include creating issues, converting tasks, and merging via queued CI.
AI-written summary · about
chapters (9)
- 0:00DevOps and collaboration
- 6:45DevOps cultural shift
- 11:18Developer experience
- 22:03GitHub team collaboration
- 33:21GitHub non-coding tools
- 36:49Code review best practices
- 42:51GitHub search and filtering
- 48:25Takeaways for collaboration
- 53:20Q&A
related talks
31mDevOps 2.0 - Bigger, Badder with More Automation
46mDevOps for Java Developers (or maybe against them?!)
01h 01m"Doing Devops" as a politically powerless developer
37mDevOps, 12 Factor and Platform Engineering
43mDevOps 2.0 - Bigger, Badder with More Automation
39mPutting the Ops in DevOps
30mIf DevOps Is Culture, Why Does Everyone Only Talk About Tools?
41mDevOps for Java Developers (or maybe against them?!)