Curated articles, resources, tips and trends from the DevOps World.
Summary: This is a summary of an article originally published by the source. Read the full original article here →
When something unexpected or unplanned occurs that creates an adverse effect on the system, I define that action as an incident. Some companies reserve the term incident for large catastrophic events, but with this broader definition you get to increase the learning opportunities on your team when an incident occurs.
If you see this happening in your organization then it’s likely that you live in a culture of blame and retribution.
The pattern with other line of thinking is that you’re discussing problems in the system versus problems in the individual.
Again, incidents have mounds of information in them, and being able to document a failure in enough detail could go a long way to training engineers in the future.
Made with pure grit © 2024 Jetpack Labs Inc. All rights reserved. www.jetpacklabs.com