SESSION + Live Q&A
Avoiding Getting on the News by Investigating Near Misses
I have a colleague at work who is obsessed about planes. There is almost no work situation that does not have an aviation based analogy. Surprisingly, this is less tiresome than you might imagine because people generally care a very great deal about planes crashing, and so a great deal of thought has gone into thinking about how to prevent disasters, and that’s useful in work context.
One such aviation example not just doing “root cause analysis” on actual crashes, but investigating literally anything that is a bit odd. This is important because actual crashes tend to be caused by multiple factors, or by things getting worse over time, so we can investigate problems one by one, or get in early, without the need for disasters that get on the news.
The relevance to software engineering is one of support. Yes, we are all over crashes and making sure they never happen again the same way, but what about the “near misses”? In order to investigate those we need to instrument our product, monitor those stats, and dig into everything that doesn’t look right. I’ll talk through some real world examples of doing just that by extracting every last drop of field information to prevent disasters, rather than waiting for them.
Speaker
Ed Holland
Software Development Manager @metaswitch
Ed has 20 years experience at Metaswitch as of a mix of Java Dev, Tech Lead, Architect, Scrum Master, Project Manager, Product Owner, and Agile Coach. However, more recently he has discovered how much fun it is to be a trouble maker, driving and inspiring change.
Read moreFind Ed Holland at:
Location
Mountbatten, 6th flr.
Track
Surviving Uncertainty: GDPR, Brexit, or Politics? Beyond DR
Topics
LondonShare
From the same track
Choosing Kubernetes: Managing Risk in Cloud Infrastructure
DBaaS and other similar products sit at the centre of a flow of risk delegation from end users at the top, all the way down to hardware manufacturers at the bottom. I’m going to tell the story of how our system developed, both the product and the implementation, in terms of the decisions...
Ben Butler-Cole
Programmer @neo4j
Balancing Risk and Psychological Safety
Engineers and people working in the software engineering industry have overall been dedicated to lifelong learning, and therefore it is imperative that companies offer support via creating a learning organisation. In this talk, Andrea will focus on understanding the principles of the...
Andrea Dobson- Kock
Counseling psychologist/GZ psychologist @containersoluti
Risk of Climate Change and What Tech Can Do
The presentation updates what we know as the science of abrupt climate change continues unraveling the details of humanity's collision with nature. After scaring the hell out of the audience with the burden of awareness, several bold visions are very briefly shared, visions to slow down the pace...
Jason Box
Climatologist & Professor in Glaciology at The Geologic Survey of Denmark and Greenland (GEUS)
Paul Johnston
CEO @roundaboutlabs
Change Is The Only Constant
The technical landscape in Skyscanner is always changing - new products, new levels of scale, new challenges. We know we're always going to have to be adapting, so we've set ourselves up to make that a bit easier. I've picked out a few real-world examples from Skyscanner where I think the...
Stuart Davidson
Tribe Lead of Production Platform @Skyscanner
Uncertainty Open Space
Shane Hastie
Director of Agile Learning Programs @ICAgile