We Already Have Nice Things, Use Them!
summary
Consulting across many companies reveals pervasive custom ops tools that cause single-point-of-failure risk, undocumented code, missing tests and slower onboarding; common replacements are industry tools like spinnaker for deployment, ansible for configuration and chef for standard CM, but migrating takes roughly twice the optimistic estimate and requires time for testing, docs, and maintenance planning. Recommend polling community, weighing proprietary vs open source, forking unmaintained projects, keeping new tools small, and treating ops tooling with app-level standards.
AI-written summary · about
chapters (8)
- 0:00Start
- 1:53Relying on in-house ops tools introduces risk
- 2:06How many people have dug through the source code of the tools you rely on?
- 3:18There are better ways for operations to provide value to the business than maintaining in-house tools.
- 8:02Allow enough time in your sprints for feature requests
- 9:14Allow time to research open source alternatives on a quarterly basis
- 10:47Open source your tool!
- 11:33Questions?
related talks
32mTales from the DevOps Transformation Trenches
25mFrom Ops to Impact: Scaling Engineering Velocity
40mPlatform Wars: The Battle Between Golden Paths and Spaghetti Pipelines
54mDeveloper experience platforms
19mMore Isn't Better
30mBringing DevOps Success to Every App, Tool & Role in Your Org
13mNavigating the infrastructure skills gap for DevOps teams
45mThe DevOps Revolution: We Haven't Always Known Everything