- How incidents can be considered an opportunity to gather context and skill
- What leaders can do to make this mindset part of the culture of an organization and encourage it across teams? (team-first thinking)
- Obstacles
- How to get the best value from incidents
Incidents are a great opportunity to gather both context and skill. They take people out of their day-to-day roles and force ephemeral teams together to solve unexpected and challenging problems. Incidents can be a great accelerator. Writing code that fails safely and loudly is one of the key differentiators for more senior engineers, and there's no better way to learn how than seeing all the different ways that systems fail.
Lisa is a product engineer at
incident.io - in fact Lisa was employee #2. Lisa started out as a consultant working at Accenture, before accidentally becoming a developer.
Lisa loves building stuff, but is also interested in how people interact with each other in a work environment - particularly in software engineering. Having seen the ‘old way’ of large-scale waterfall project at Accenture, Lisa thinks it’s interesting to try and bring some thinking from that environment into a startup. Outside of work, Lisa loves cooking and pretty much any competitive sport (well, the British ones anyway).
Voted Best 25 DevOps Podcasts by
Feedspot
Want access to more content like this? Gain the tools, resources and knowledge to help your organization adapt and respond to challenges by becoming a member of DevOps Institute. Engage in one of the fastest-growing DevOps communities today! Get started for free:
https://www.devopsinstitute.com/membership/
Have questions, feedback or just want to chat? Send us an email at
podcast@devopsinstitute.com
