Building Enterprise Software Today: A partnership in openness
summary
Claims that enterprise engineering must be rebuilt around collaboration not secrecy with concrete changes: a 239‑engineer team split into ~50 scrum squads, customers invited onto standups and playbacks, no closed source repo (all engineers can PR), a Definition of Done requiring 90% automated tests and APIs for every action so there are effectively no testers, containers on Docker/Kubernetes and microservices that must run on a Raspberry Pi, and a server‑side “Muse” greasemonkey that lets customers submit patches into CI/CD. Eat the puffer fish and open everything.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 1:54Pufferfish
- 5:00The epiphany
- 6:41Vergence
- 7:27Howl
- 13:45The ivory tower
- 18:37Openness
- 23:35Deployment models
- 26:18Why do I care
- 26:28Be bold
- 30:01Communities
- 31:34Running on Raspberry Pi
- 33:41Versions of software
- 40:16Building software
- 42:14Docker Enterprise
- 50:24API
- 52:04Live Grid
related talks
27mTransforming Traditional Enterprise Software Development Processes
14mKeynote: Open Source & Operational Excellence
05mAdventures In Enterprise: Lessons Learned Promoting DevOps In A Legacy Organization
30mAn Evolutionary Approach to DevOps
42mRadical Transparency: Lessons From Open-Sourcing Nearly All Company Documenta...
44mBringing Open-Source Brilliance to Scrum Teams: A Guide to Enhanced Collaboration
39mGetting started with internal open source
32mMastering Enterprise Open Source for Cloud and Vendor Independence