Deduplicating an Organization
summary
Comcast frames the problem as eliminating redundant engineering work and builds consensus with charters, Slack arch-W channels and architecture ADRs that capture context rationale and consequences; working groups publish decisions only for technologies already running in production. The team of 4–5 people produces reference implementations (notably the lab week portal) and chooses stack pieces — e.g. enterprise source control and Concourse CI/CD — to reduce undifferentiated lifting, speed delivery, cut costs and surface tradeoffs so teams can adopt or extend the chosen solutions.
AI-written summary · about
chapters (16)
- 0:00Intro
- 3:37What is Deduplication
- 7:35Why do we want to do this
- 9:32Leadership
- 11:12Software Strategy
- 13:36Collaboration
- 15:24Reference implementations
- 17:22Architecture gills
- 19:26Announcements
- 21:07ADR Format
- 21:51Solutions
- 22:40Consensus
- 23:52Solution Selection
- 24:30Learnings
- 26:08Summary
- 27:11Questions
related talks
25mChanging the Development Culture at Comcast and Our Evolution from Legacy SOA to Cloud Native
30mThe future of Dev[Sec]Ops transformation
23mKeynote: How Comcast is Putting Customers First - Powered by Cloud Foundry
08mKeynote: How Comcast is Working to Transform our Product Delivery Experience
53mFrom DevOps to DevSecOps
22mScaling Culture of Resiliency in the Enterprise at Charter Communications
04mPaul Cleary Interview
30mBuilding an Enterprise DevOps Community