Journey Of Devops Teams in a Corporate Environment
summary
Two DevOps teams over five years hit the same blockers: a tool explosion and brittle documentation that creates knowledge silos. The fix is concrete: standardize artifacts as AsciiDoc text in each repo, ban IDE project files via .gitignore, publish a static microsite and Word/PDF with GitLab CI/CD and Asciidoctor, and keep examples in the simplest form (bash/curl) so any of the five developers can reproduce them. Results: automatable versioning, searchable docs, lower onboarding cost and fewer single-person failures.
AI-written summary · about
chapters (8)
- 0:00Intro
- 0:30Contents
- 0:56Devops Production Model
- 2:49Knowledge silos
- 9:00Documentation
- 13:06Include
- 15:23Integration
- 19:17Recap
related talks
41mThe Introduction of DevOps in Large-Scale Organizations
30mTurning Around the Containership
25mBuilding Docs like Code: Continuous Integration for Documentation
55mDevOps isn't just about developing
29mDevOps Mindset Transformation
34mYou only have to change one thing to do the DevOps
47mTales from the Dev Side: What Went Wrong, What We Fixe & What You Can Steal
32mTales from the DevOps Transformation Trenches