John Allspaw's guest appearances

John Allspaw

PreAccident Investigation Podcast

Software Engineering Daily

Software Engineering Radio - the podcast for professional software developers

Greater Than Code

Cloud Engineering Archives - Software Engineering Daily

USI - Les sessions - iPhone/iPod

USI - Les sessions - iPad / Apple TV

Screaming in the Cloud

Podcast Archives - Software Engineering Daily

The Engineering Leadership Podcast

What the Dev?

Page it to the Limit

Software Daily

Resilience in Action

Naturalistic Decision Making 

Corey Quinn

Tim Banks

Liz Fong-Jones

Kent Beck

Ben Sigelman

Kelsey Hightower

Steren Giannini

Nader Dabit

Anurag Gupta

Pete Cheslock

Matt Ward

Vlad Ionescu

Grant Miller

Anurag Goel

Kartik Mathur

OwlTail

We cover resilience engineering &amp; learning from incidents with John Allspaw, former CTO @ Etsy and current Founder &amp; Principal @ Adaptive Capacity Labs! Co-hosted by Kenji Kiuchi (Head of Quality and Performance @ Postman) this episode also addresses common unintuitive perspectives within resilience engineering, strategies for effective incident response / problem solving, how to identify current sources of resilience, and practical tips for implementing these resiliency tactics in your organization today.ABOUT JOHN ALLSPAWJohn Allspaw (@allspaw) has worked in software systems engineering and operations for over twenty years in many different environments. John’s publications include the books The Art of Capacity Planning (2009) and Web Operations (2010) as well as the forward to “The DevOps Handbook.”  His 2009 Velocity talk with Paul Hammond, “10+ Deploys Per Day: Dev and Ops Cooperation” helped start the DevOps movement. John served as CTO at Etsy, and holds an MSc in Human Factors and Systems Safety from Lund University."The competitive advantage is not for a leader to say, ‘Why did it take so long to restore this issue or resolve this outage?’ A competitive advantage is, ‘Oh my God, that is amazing. Tell me what made this hard and what are any of the things that made it difficult to resolve? Is there anything I can do to help get out of the way for people to do the work?’"- John Allspaw   ABOUT KENJI KIUCHIKenji Kiuchi (@dr_kiuchi) is Head of Quality and Performance at Postman, an API platform whose mission is to maximize everyone's creativity through the power of connected software. There he leads a global team with a focus on maximizing user delight and innovating the practice of testing. Before coming to Postman, he spent several years ‘Helping people get Jobs” at Indeed. There, he worked on scaling teams and practice to optimize engineering delivery as well as leading Diversity, Inclusion and Belonging initiatives as an Associate Site Director. Prior to Indeed, Kenji spent several years as an Engineering Manager at Twitter where he led Quality efforts across monetization, growth, infra and the delivery of live video. When Kenji isn’t driving engineering excellence, he’s driving his motorcycle, spending quality time with his 3 daughters, and mentoring leaders across the globe.Check out our friends and sponsor, JellyfishTo learn more about Jellyfish and how they can help you increase engineering satisfaction and create happier, higher-performing engineering teams...Learn more at Jellyfish.co/elcSHOW NOTES:John’s perspective on production (4:27)What drove John toward resilience engineering (6:22)How complex systems relate to resilience engineering (9:23)Differences between robustness and resilience (13:13)The role of productive adaptation in resilience engineering (17:26)Identify sources of resilience already present in your organization (22:52)Examples of unintuitive perspectives involving incident analysis (27:15)How to make room for unintuitive perspectives (31:41)Practical tips for implementing resiliency tactics &amp; understanding incidents (36:12)Rapid fire questions (39:51)LINKS AND RESOURCESLearning From Incidents Conference 2023 - This is a forum for sharing stories of incidents, incident handling, and the learnings from software engineers who handle large-scale distributed software systems.Hindsight and Sacrifice Decisions Blog Post on Adaptive Capacity Labs reaction to the NYSE halting trading to resolve an issueUsing Language by Herbert H. Clark - Herbert Clark argues that language use is more than the sum of a speaker speaking and a listener listening. It is the joint action that emerges when speakers and listeners, writers and readers perform their individual actions in coordination, as ensembles. In contrast to work within the cognitive sciences, which has seen language use as an individual process, and to work within the social sciences, which has seen it as a social process, the author argues strongly that language use embodies both individual and social processes.Papers We Love TalkVisual Momentum

<p>We cover resilience engineering &amp; learning from incidents with John Allspaw, former CTO @ Etsy and current Founder &amp; Principal @ Adaptive Capacity Labs! Co-hosted by Kenji Kiuchi (Head of Quality and Performance @ Postman) this episode also addresses common unintuitive perspectives within resilience engineering, strategies for effective incident response / problem solving, how to identify current sources of resilience, and practical tips for implementing these resiliency tactics in your organization today.</p><h2><strong>ABOUT</strong> <a href="https://www.linkedin.com/in/jallspaw/" rel="nofollow" target="_blank"><strong>JOHN ALLSPAW</strong></a></h2><p>John Allspaw (<a href="https://twitter.com/allspaw" rel="nofollow" target="_blank">@allspaw</a>) has worked in software systems engineering and operations for over twenty years in many different environments. John’s publications include the books The Art of Capacity Planning (2009) and Web Operations (2010) as well as the forward to “The DevOps Handbook.”  His 2009 Velocity talk with Paul Hammond, “10+ Deploys Per Day: Dev and Ops Cooperation” helped start the DevOps movement. John served as CTO at Etsy, and holds an MSc in Human Factors and Systems Safety from Lund University.</p><blockquote><p>"The competitive advantage is not for a leader to say, ‘Why did it take so long to restore this issue or resolve this outage?’ A competitive advantage is, ‘Oh my God, that is amazing. Tell me what made this hard and what are any of the things that made it difficult to resolve? Is there anything I can do to help get out of the way for people to do the work?’"</p><p>- John Allspaw   </p></blockquote><h2><strong>ABOUT</strong> <a href="https://www.linkedin.com/in/kenjikiuchi/" rel="nofollow" target="_blank"><strong>KENJI KIUCHI</strong></a></h2><p>Kenji Kiuchi (<a href="https://twitter.com/dr_kiuchi" rel="nofollow" target="_blank">@dr_kiuchi</a>) is Head of Quality and Performance at Postman, an API platform whose mission is to maximize everyone's creativity through the power of connected software. There he leads a global team with a focus on maximizing user delight and innovating the practice of testing. Before coming to Postman, he spent several years ‘Helping people get Jobs” at Indeed. There, he worked on scaling teams and practice to optimize engineering delivery as well as leading Diversity, Inclusion and Belonging initiatives as an Associate Site Director. Prior to Indeed, Kenji spent several years as an Engineering Manager at Twitter where he led Quality efforts across monetization, growth, infra and the delivery of live video. When Kenji isn’t driving engineering excellence, he’s driving his motorcycle, spending quality time with his 3 daughters, and mentoring leaders across the globe.</p><h2><strong>Check out our friends and sponsor,</strong> <a href="https://www.notion.so/sfelc/Jellyfish.co/elc" rel="nofollow" target="_blank"><strong>Jellyfish</strong></a></h2><p>To learn more about Jellyfish and how they can help you increase engineering satisfaction and create happier, higher-performing engineering teams...</p><h3><strong>Learn more at</strong> <a href="http://jellyfish.co/elc" rel="nofollow" target="_blank"><strong>Jellyfish.co/elc</strong></a></h3><h2><strong>SHOW NOTES:</strong></h2><ul><li>John’s perspective on production (4:27)</li><li>What drove John toward resilience engineering (6:22)</li><li>How complex systems relate to resilience engineering (9:23)</li><li>Differences between robustness and resilience (13:13)</li><li>The role of productive adaptation in resilience engineering (17:26)</li><li>Identify sources of resilience already present in your organization (22:52)</li><li>Examples of unintuitive perspectives involving incident analysis (27:15)</li><li>How to make room for unintuitive perspectives (31:41)</li><li>Practical tips for implementing resiliency tactics &amp; understanding incidents (36:12)</li><li>Rapid fire questions (39:51)</li></ul><h2>LINKS AND RESOURCES</h2><ul><li><a href="https://www.learningfromincidents.io/learning-from-incidents-conference-2023" rel="nofollow" target="_blank">Learning From Incidents Conference 2023</a> - This is a forum for sharing stories of incidents, incident handling, and the learnings from software engineers who handle large-scale distributed software systems.</li><li><a href="https://www.adaptivecapacitylabs.com/blog/2019/03/03/hindsight-and-sacrifice-decisions/" rel="nofollow" target="_blank">Hindsight and Sacrifice Decisions</a> Blog Post on Adaptive Capacity Labs reaction to the NYSE halting trading to resolve an issue</li><li><a href="https://www.amazon.com/Using-Language-Herbert-H-Clark/dp/0521567459" rel="nofollow" target="_blank">Using Language by Herbert H. Clark</a> - Herbert Clark argues that language use is more than the sum of a speaker speaking and a listener listening. It is the joint action that emerges when speakers and listeners, writers and readers perform their individual actions in coordination, as ensembles. In contrast to work within the cognitive sciences, which has seen language use as an individual process, and to work within the social sciences, which has seen it as a social process, the author argues strongly that language use embodies both individual and social processes.</li><li><a href="https://youtu.be/KgC_N9glqMs" rel="nofollow" target="_blank">Papers We Love Talk</a></li><li><a href="https://link.springer.com/referenceworkentry/10.1007/978-0-387-35973-1_1453#Sec3" rel="nofollow" target="_blank">Visual Momentum</a></li></ul>

Resilience engineering, learning from incidents and unintuitive perspectives on incident analysis w/ John Allspaw #116

Resilience

John Allspaw has worked in software systems engineering and operations for over twenty years in many different environments. He authored the books The Art of Capacity Planning and Web Operations, as well as the forward to The DevOps Handbook. John’s 2009 Velocity talk with Paul Hammond, 10+ Deploys Per Day: Dev and Ops Cooperation, is credited for helping start the DevOps movement. John served as CTO at Etsy and holds an MSc in Human Factors and Systems Safety from Lund University.

<p><b>John Allspaw has worked in software systems engineering and operations for over twenty years in many different environments. He authored the books </b><b><em>The Art of Capacity Planning</em></b><b> and </b><b><em>Web Operations</em></b><b>, as well as the forward to </b><b><em>The DevOps Handbook</em></b><b>. John’s 2009 Velocity talk with Paul Hammond, </b><b><em>10+ Deploys Per Day: Dev and Ops Cooperation,</em></b><b> is credited for helping start the DevOps movement. John served as CTO at Etsy and holds an MSc in Human Factors and Systems Safety from Lund University.</b></p>

Resilience in Action E14: Resilience Is the Audacity of Adaptive Capacity ft. John Allspaw

Finding a Common Language for Incidents with John Allspaw 

Corey Quinn is guest hosting on Software Engineering Daily this week, presenting a Tour of the Cloud. Corey Quinn is the Chief Cloud Economist at The Duckbill Group, where he helps companies fix their AWS bill by making it smaller and less horrifying. If you’re looking to lower your AWS bill or negotiate a new

Digital Ocean with John Allspaw

Corey Quinn is guest hosting on Software Engineering Daily this week, presenting a Tour of the Cloud. Corey Quinn is the Chief Cloud Economist at The Duckbill Group, where he helps companies fix their AWS bill by making it smaller and less horrifying. If you’re looking to lower your AWS bill or negotiate a new contract with AWS, you can learn more about The Duckbill Group’s services at https://www.duckbillgroup.com/.  Corey is also the host and creator of Last Week in AWS, which publishes newsletters and podcasts covering topics to help you stay up to date on all things AWS and insightful conversations with experts in the world of cloud computing all delivered lovingly with Corey’s infamous snark. Subscribe at https://www.lastweekinaws.com and follow Corey on Twitter @QuinnyPig.  In this episode, Corey Quinn interviews John Allspaw, Founder and Principal of Adaptive Capacity Labs. The post Digital Ocean with John Allspaw appeared first on Software Engineering Daily.

<p><em>Corey Quinn is guest hosting on Software Engineering Daily this week, presenting a Tour of the Cloud. </em><em>Corey Quinn is the Chief Cloud Economist at The Duckbill Group, where he helps companies fix their AWS bill by making it smaller and less horrifying. If you’re looking to lower your AWS bill or negotiate a new contract with AWS, you can learn more about The Duckbill Group’s services at </em><a href="https://www.duckbillgroup.com/" rel="noopener noreferrer nofollow" target="_blank"><em>https://www.duckbillgroup.com/</em></a><em>. </em></p> <p><em>Corey is also the host and creator of Last Week in AWS, which publishes newsletters and podcasts covering topics to help you stay up to date on all things AWS and insightful conversations with experts in the world of cloud computing all delivered lovingly with Corey’s infamous snark. Subscribe at </em><a href="https://www.lastweekinaws.com/" rel="noopener noreferrer nofollow" target="_blank"><em>https://www.lastweekinaws.com</em></a><em> and follow Corey on Twitter @QuinnyPig. </em></p> <p>In this episode, Corey Quinn interviews John Allspaw, Founder and Principal of Adaptive Capacity Labs.</p> <p>The post <a href="https://softwareengineeringdaily.com/2021/06/10/digital-ocean-with-john-allspaw/" rel="nofollow" target="_blank">Digital Ocean with John Allspaw</a> appeared first on <a href="https://softwareengineeringdaily.com" rel="nofollow" target="_blank">Software Engineering Daily</a>.</p>

John Allspaw is the founder of Adaptive Capacity Labs and one of the people that drove DevOps movement from its beginnings. His (and Paul Hammond’s) famous “10+ deploys per day at Flickr” talk at Velocity conf in 2009 showed us that there is a better way of collaborating and delivering software. Today, John focuses on helping organizations do better in incident management and learn from their own mistakes. I talked with John about incident management, learning organizations, and how the world has changed since 2009.Subscribe to 0800-DEVOPS newsletter here.Show notes:This interview is featured in 0800-DEVOPS #17 - John Allspaw, resilience engineering and DOES 2020 conference.The community sharing stories and learning from incidents.

0800-DEVOPS

<p><a href="https://twitter.com/allspaw" rel="nofollow" target="_blank">John Allspaw</a> is the founder of Adaptive Capacity Labs and one of the people that drove DevOps movement from its beginnings. His (and Paul Hammond’s) famous “10+ deploys per day at Flickr” talk at Velocity conf in 2009 showed us that there is a better way of collaborating and delivering software. Today, John focuses on helping organizations do better in incident management and learn from their own mistakes. I talked with John about incident management, learning organizations, and how the world has changed since 2009.<br/><br/>Subscribe to 0800-DEVOPS newsletter <a href="https://croz.net/0800-devops/" rel="nofollow" target="_blank">here</a>.<br/><br/>Show notes:</p><ul><li>This interview is featured in <a href="https://croz.net/news/0800-devops-17-john-allspaw-resilience-engineering-and-does-2020-conference/" rel="nofollow" target="_blank">0800-DEVOPS #17 - John Allspaw, resilience engineering and DOES 2020 conference</a>.</li><li>The community sharing stories and <a href="https://www.learningfromincidents.io/" rel="nofollow" target="_blank">learning from incidents</a>.</li></ul>

Learning from incidents with John Allspaw

We spoke to John Allspaw, the principal and founder of Adaptive Capacity Labs, a consulting company that helps organizations deal with data incidents, to talk about the growing concept of resilience engineering.In a nutshell, reverse engineering is concerned with adverse external events that can lead to system failure. It tests how much an organization can withstand stress and other challenging factors to continue performing its core functions and avoid loss of data.Be sure to check out Allspaw's talk at the DevOps Enterprise SummitLas Vegas on October 13th to learn more! 

<p>We spoke to John Allspaw, the principal and founder of Adaptive Capacity Labs, a consulting company that helps organizations deal with data incidents, to talk about the growing concept of resilience engineering.<br/><br/>In a nutshell, reverse engineering is concerned with adverse external events that can lead to system failure. It tests how much an organization can withstand stress and other challenging factors to continue performing its core functions and avoid loss of data.<br/><br/>Be sure to check out Allspaw's talk at the <a href="https://events.itrevolution.com/virtual/?utm_medium=referral&amp;utm_source=sdtimes&amp;utm_term=sdtimes-does20us-virtual-email-newsletter-1&amp;utm_content=onsale&amp;utm_campaign=does20us" rel="nofollow" target="_blank">DevOps Enterprise Summit<br/>Las Vegas </a>on October 13th to learn more! </p>

What the Dev(Ops)? - Why resilience engineering can help your organization continue core functions despite stress with John Allspaw - Episode 59

John Allspaw joins us this week to talk about incident response, and helping organizations build their own NTSB (the National Transportation Safety Board, a US government agency that investigates transportation accidents). Introduction John gives us an overview of what he and the other folks at Adaptive Capacity Labs are working on. State of the Industry John talks about the state of the industry around incident response. Learning from incidents is happening; but are organizations supporting it? Are people finding it helpful? Expertise is coming from inside the house, in that software practitioners are getting better at coping with the complexity of the systems. Where there is still work to do is around how teams learn from their incidents and postmortems. Are the artifacts generated by these exercises used after they are created, or do they just become a museum to the incidents? Who are the Incident Nerds There is an emerging community of folks who are really enthusiastic about learning from other organizations' incidents, in software and across different kinds of industries. But many incident reports are still written to be filed rather than written to be read, and leave out some of the other aspects of an incident that are important. In addition to just whatever triggered the incident, there are other aspects to be learned from, like weighing potential fixes, or finding information. Thinking about incident reports as a story, what elements make it a good story? What did the team struggle with? What was hard about it? What are We Learning from Other Industries? A number of “safety critical” domains have a longer history than software development with respect to dealing with incidents. Some domains have different constraints, challenges for gathering data, legal ramifications. What will the future look like, and can software development avoid some of those constraints. How do all of these potential incidents impact not just the employees on the teams managing the incidents, but also the public, consumers, and how are they impacted by an outage? Are consumers able to make informed decisions about a company based on how incidents are handled? As a learning exercise, do your new employees take the opportunity to read past incident reports and then ask questions? Debunking a Myth John deflects answering about Root Cause. You’ll just have to check Twitter. An existing belief that leads people to a potentially incorrect outcome, is that an incident is seen by different people, with different perspectives, as different. There is not one true universal story that everyone will get from reading an incident analysis. The goal shouldn’t be for just the person doing the analysis to understand what happened, but to also make future readers understand what happened. What Do You Wish You’d Known Earlier in Your Career? John talks about the practice of software engineering, and the certainty that things has changed and will change. Everything should be up for questioning of assumptions about what is the best way for something to be done. What Are You Glad We Didn’t Ask? John talks a bit about incident command frameworks and refers to Laura Maguire’s research on the costs of coordination and how the costs associated with robust incident response are easy to forget. Laura’s talk is linked in the Additional Resources below. Additional Resources  PagerDuty Home Page PagerDuty Summit John’s Talk from PagerDuty Summit 2018 Read some incident reviews collected by the folks at Incident Labs Learning From Incidents Laura Maguire’s talk on the Costs of Coordination from QCon London 2020 Episode transcribed by Rev

<p>John Allspaw joins us this week to talk about incident response, and helping organizations build their own NTSB (the National Transportation Safety Board, a US government agency that investigates transportation accidents).</p> <h3>Introduction</h3> <p>John gives us an overview of what he and the other folks at Adaptive Capacity Labs are working on.</p> <h3>State of the Industry</h3> <p>John talks about the state of the industry around incident response. Learning from incidents is happening; but are organizations supporting it? Are people finding it helpful? Expertise is coming from inside the house, in that software practitioners are getting better at coping with the complexity of the systems. Where there is still work to do is around how teams learn from their incidents and postmortems. Are the artifacts generated by these exercises used after they are created, or do they just become a museum to the incidents?</p> <h3>Who are the Incident Nerds</h3> <p>There is an emerging community of folks who are really enthusiastic about learning from other organizations' incidents, in software and across different kinds of industries. But many incident reports are still written to be filed rather than written to be read, and leave out some of the other aspects of an incident that are important. In addition to just whatever triggered the incident, there are other aspects to be learned from, like weighing potential fixes, or finding information.</p> <p>Thinking about incident reports as a story, what elements make it a good story? What did the team struggle with? What was hard about it?</p> <h3>What are We Learning from Other Industries?</h3> <p>A number of “safety critical” domains have a longer history than software development with respect to dealing with incidents. Some domains have different constraints, challenges for gathering data, legal ramifications. What will the future look like, and can software development avoid some of those constraints.</p> <p>How do all of these potential incidents impact not just the employees on the teams managing the incidents, but also the public, consumers, and how are they impacted by an outage? Are consumers able to make informed decisions about a company based on how incidents are handled?</p> <p>As a learning exercise, do your new employees take the opportunity to read past incident reports and then ask questions?</p> <h3>Debunking a Myth</h3> <p>John deflects answering about Root Cause. You’ll just have to check Twitter.</p> <p>An existing belief that leads people to a potentially incorrect outcome, is that an incident is seen by different people, with different perspectives, as different. There is not one true universal story that everyone will get from reading an incident analysis.</p> <p>The goal shouldn’t be for just the person doing the analysis to understand what happened, but to also make future readers understand what happened.</p> <h3>What Do You Wish You’d Known Earlier in Your Career?</h3> <p>John talks about the practice of software engineering, and the certainty that things has changed and will change. Everything should be up for questioning of assumptions about what is the best way for something to be done.</p> <h3>What Are You Glad We Didn’t Ask?</h3> <p>John talks a bit about incident command frameworks and refers to Laura Maguire’s research on the costs of coordination and how the costs associated with robust incident response are easy to forget. Laura’s talk is linked in the Additional Resources below.</p> <h3>Additional Resources</h3> <ul> <li><a href="https://www.pagerduty.com/" rel="nofollow" target="_blank">PagerDuty Home Page</a></li> <li><a href="https://bit.ly/summit_community" rel="nofollow" target="_blank">PagerDuty Summit</a></li> <li><a href="https://www.adaptivecapacitylabs.com/blog/2018/11/05/incidents-as-we-imagine-them-versus-how-they-actually-are/" rel="nofollow" target="_blank">John’s Talk from PagerDuty Summit 2018</a></li> <li><a href="https://zine.incidentlabs.io/" rel="nofollow" target="_blank">Read some incident reviews collected by the folks at Incident Labs</a></li> <li><a href="https://www.learningfromincidents.io/" rel="nofollow" target="_blank">Learning From Incidents</a></li> <li><a href="https://qconlondon.com/london2020/presentation/how-many-too-much-exploring-costs-coordination-during-outages" rel="nofollow" target="_blank">Laura Maguire’s talk on the Costs of Coordination from QCon London 2020</a></li> <li>Episode transcribed by <a href="https://www.rev.com" rel="nofollow" target="_blank">Rev</a></li></ul>