Podcast appearances and mentions of Paul Hammond

On this Screaming in the Cloud Replay, Corey is joined by John Allspaw, Founder/Principal at Adaptive Capacity Labs. John was foundational in the DevOps movement, but he's continued to bring much more to the table. He's written multiple books and seems to always be at the forefront. Which is why he is now at Adaptive Capacity Labs. John tells us what exactly Adaptive Capacity Labs does and how it works and how he convinced some heroes to get behind it. John brings a much-needed insight into how to get multiple people in an organization on the same level when it comes to dealing with incidents. Engineers and non. John points out the issues surrounding public vs. private write-ups and the roadblocks they may prop up. Adaptive Capacity Labs is working towards bringing those roadblocks down, tune in for how!Show Highlights(0:00) Introduction(0:59) The Duckbill Group sponsor read(1:33) What is Adaptive Capacity Labs and the work that they do?(3:00) How to effectively learn from incidents(7:33) What is the root of confusion in incident analysis(13:20) Identifying if an organization has truly learned from their incidents(18:23) Gitpod sponsor read(19:35) Adaptive Capacity Lab's reputation for positively shifting company culture(24:22) What the tech industry is missing when it comes to learning effectively from the incidents(28:44) Where you can find more from John and Adaptive Capacity LabsAbout John AllspawJohn 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 UniversityLinksThe Art of Capacity Planning: https://www.amazon.com/Art-Capacity-Planning-Scaling-Resources/dp/1491939206/Web Operations: https://www.amazon.com/Web-Operations-Keeping-Data-Time/dp/1449377440/The DevOps Handbook: https://www.amazon.com/DevOps-Handbook-World-Class-Reliability-Organizations/dp/1942788002/Adaptive Capacity Labs: https://www.adaptivecapacitylabs.comJohn Allspaw Twitter: https://twitter.com/allspawRichard Cook Twitter: https://twitter.com/ri_cookDave Woods Twitter: https://twitter.com/ddwoods2Original Episodehttps://www.lastweekinaws.com/podcast/screaming-in-the-cloud/finding-a-common-language-for-incidents-with-john-allspaw/SponsorsThe Duckbill Group: duckbillgroup.com Gitpod: http://www.gitpod.io/

We reflect on the rise of DevOps and the frustrating dynamics that led to it. Plus, tech's latest bright idea: Roombas with attitude.

For the focus of this week's episode, see the attached guitar meme from @SongStoriesRewind which casts a wide net, and sparks the discussion of axes and their masters. Paul Hammond knows both ends of that stick! His long history as a founding member of the top-shelf Led Zeppelin tribute, Get The Led Out is part of the discussion (see Jimmy Page double-neck!), as is his love and knowledge of guitars. Get details about the band's upcoming shows we discussed, and to keep up with the band RIGHT HERE! Red Rocks, the legendary venue, comes up this week, too! Here's a link to last year's visit for the band! Hit Get The Led Out's website here, and get to a show near you! Learn more about your ad choices. Visit megaphone.fm/adchoices

For the focus of this week's episode, see the attached guitar meme from @SongStoriesRewind which casts a wide net, and sparks the discussion of axes and their masters. Paul Hammond knows both ends of that stick! His long history as a founding member of the top-shelf Led Zeppelin tribute, Get The Led Out is part of the discussion (see Jimmy Page double-neck!), as is his love and knowledge of guitars. Get details about the band's upcoming shows we discussed, and to keep up with the band RIGHT HERE! Red Rocks, the legendary venue, comes up this week, too! Here's a link to last year's visit for the band! Hit Get The Led Out's website here, and get to a show near you! Learn more about your ad choices. Visit megaphone.fm/adchoices

"Caring for Elderly Parents Who Live Alone : The I Am Fine Product Story" shares a son's innovative solution for monitoring his mom's wellbeing from across the country. As a tech entrepreneur, he leveraged his expertise to develop the I Am Fine system - providing peace of mind for families with elderly parents living independently. Learn how this simple daily call check-in, with customizable call times and backup alerts, can eliminate the stress of juggling your own life demands while ensuring your elderly parent is safe. Gain insights into using technology to support aging in place, prevent isolation, and embrace your loved one's independence, all while safeguarding their health from afar. If you're a long-distance caregiver for elderly parents, this episode offers a practical solution. Our Guest - Paul Hammond Iamfine is the brainchild of Colin and Paul Hammond. Colin lives in the UK while his brother Paul lives on the west coast of America. They designed Iamfine to help them both keep in touch with their mother Isobel who lives alone in Florida. The brothers regularly speak to their mother and visit several times a year, but busy schedules mean they struggle to check on her every day. Although in her mid-90s, Isobel is healthy, plays golf twice a week, lives in her own home and loves life. Like many elderly people living alone, she is fiercely independent and doesn't want her sons to be worrying about her.

"Caring for Elderly Parents Who Live Alone : The I Am Fine Product Story" shares a son's innovative solution for monitoring his mom's wellbeing from across the country. As a tech entrepreneur, he leveraged his expertise to develop the I Am Fine system - providing peace of mind for families with elderly parents living independently. Learn how this simple daily call check-in, with customizable call times and backup alerts, can eliminate the stress of juggling your own life demands while ensuring your elderly parent is safe. Gain insights into using technology to support aging in place, prevent isolation, and embrace your loved one's independence, all while safeguarding their health from afar. If you're a long-distance caregiver for elderly parents, this episode offers a practical solution. Our Guest - Paul Hammond Iamfine is the brainchild of Colin and Paul Hammond. Colin lives in the UK while his brother Paul lives on the west coast of America.  They designed Iamfine to help them both keep in touch with their mother Isobel who lives alone in Florida. The brothers regularly speak to their mother and visit several times a year, but busy schedules mean they struggle to check on her every day. Although in her mid-90s, Isobel is healthy, plays golf twice a week, lives in her own home and loves life.  Like many elderly people living alone, she is fiercely independent and doesn't want her sons to be worrying about her. ++++++++++++++++++++++++++++++++++++++++ Related Episodes: Can Technology & Innovation Change Aging at Home? Independence, Security & Peace of Mind ++++++++++++++++++++++++++++++++++++++++ Sign Up for more Advice & Wisdom - email newsletter. ++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Please help us keep our show going by supporting our sponsors. Thank you. ++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Feeling overwhelmed? HelpTexts can be your pocket therapist. Going through a tough time? HelpTexts offers confidential support delivered straight to your phone via text message. Whether you're dealing with grief, caregiving stress, or just need a mental health boost, their expert-guided texts provide personalized tips and advice. Sign up for a year of support and get: Daily or twice-weekly texts tailored to your situation Actionable strategies to cope and move forward Support for those who care about you (optional) HelpTexts makes getting help easy and convenient. ++++++++++++++++++++++++++++++++++++++++ Make Your Brain Span Match Your LifeSpan Relevate from NeuroReserve I've been focusing a lot on taking care of my brain health, & I've found this supplement called RELEVATE to be incredibly helpful. It provides me with 17 nutrients that support brain function & help keep me sharp. Since you're someone I care about, I wanted to share this discovery with you. You can order it with my code: FM15 & get 15% OFF your order. With Relevate nutritional supplement, you get science-backed nutrition to help protect your brain power today and for years to come. You deserve a brain span that lasts as long as your lifespan. ++++++++++++++++++++++++++++++++++++++++ Join Fading Memories On Social Media! If you've enjoyed this episode, please share this podcast with other caregivers! You'll find us on social media at the following links. Instagram Twitter LinkedIn  Facebook Contact Jen at hello@fadingmemoriespodcast.com or Visit us at www.FadingMemoriesPodcast.com

It's easy to get stuck in the same-old, same-old.  If you're like many people these days, you might feel like you have to put your own creative, playful leanings aside for the sake of business or all the responsibilities of adult life.  Maybe somewhere along the way, you put your passion projects on the shelf. Or you started playing within your comfort zone, just doing things you're good at, rather than branching out and trying something new.  If any of this rings true for you — or if you simply want a dose of creative inspiration — check out today's podcast episode.  Fair warning, this episode is a bit unusual: rather than a traditional interview, it brings together a group of old friends who explore the lessons they learned from the ‘90s hardcore punk scene.  What can a niche subculture (and a group of aging punks) teach us? Turns out, quite a bit.  While also covering a bit of ‘90s nostalgia (big pants! Mix tapes!), Camille and her friends explore topics like: The power of community and collaboration, and why it's often better to build something together rather than entirely solo. Why the “if you build it, they will come” approach is often true; you might be surprised who shows up to support you if you put yourself out there. Inclusivity, and how to make a community feel more inviting. (Including prompts to help newbies feel included.) A great mantra and approach for starting anything new. (And how one person used it to turn their attic crawl space into an actual B&B with virtually no resources… well before Airbnb was a thing.) Why centering your life and work around your values can give you motivation and purposefulness (and how to avoid “teenage aimlessness” at any age.) Why DIY and amateur culture are so powerful; why you should embrace the things you suck and why you shouldn't feel pressure to monetize something you love if you don't want to. The magic that can happen when you find “your people” and choose to spend your time with people you genuinely love. (Plus, the proper length for any mixtape!) In this episode, you'll hear from host Camille DePutter, along with Colleen Burgess, Megan DePutter, Paul Hammond, Lukas Neville, Matt Nish-Lapidus, and Kim Walters. 

Cinephile Game Night has returned this year for Cinephile Summer, a brand new season featuring your favorite podcasters and filmmakers going head-to-head to see who is the ultimate cinephile. Hosted by The Film Stage's Jordan Raup, Conor O'Donnell, and Dan Mecca along with Cinephile: A Card Game creator Cory Everett, the series will debut new episodes bi-weekly on The Film Stage Show podcast feed and The Film Stage YouTube channel. For the fourth episode of Cinephile Summer, we were thrilled to face off against our friends at 50 MPH––a brand new podcast that takes you behind-the-scenes of Jan de Bont's Oscar-winning 1994 summer blockbuster, Speed––featuring Kris Tapley, Paul Hammond, and Jonathan Foster. Learn more: https://thefilmstage.com/cinephile Subscribe to 50MPH: https://50mphpodcast.com

Paul was a former player who I recruited to come to Arlington Catholic as a Junior. He is a kid that you build a team around because of his work ethic, attitude and commitment to being great. Paul travelled most mornings over an hour by train and bus to attend school at Arlington Catholic. He played Prep School in Georgia, played in the Post graduate All-American Game, and is now playing QB at New Haven. A great listen for all ages and a true story of hard work and dedication to a sport.

We cover resilience engineering & learning from incidents with John Allspaw, former CTO @ Etsy and current Founder & 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 & 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

A software development philosophy that emphasizes incremental delivery, team collaboration, continual planning, and continual learning  CyberWire Glossary link: https://thecyberwire.com/glossary/agile-software-development Audio reference link: "Velocity 09: John Allspaw and Paul Hammond, "10+ Deploys Pe," John Allspaw and Paul Hammond, 2009 Velocity Conference, YouTube, 25 June 2009. Learn more about your ad choices. Visit megaphone.fm/adchoices

We're back for Episode 94! In this episode Cody and Eric catch up on the news +  6 Good Tactics Games We are doing news for the first monthly episode and then "catching up" later in the month.   Episode Guide ---------------- 5:39 - Quick Questions 18:12 - Patreon Song 21:52 - Tea Time With Time 48:28 - News 1:55:30 - 6 Good Tactics Games News -     (codY) Sven Krasser game Cab Hustle no longer regulated to the Zzapp64 cover disc.   https://svenatl.itch.io/cabhustle  (Tim) - Playable demo of new racer coming on Steam real soon, SP Grand Prix by @RozzBozzy on twitter:  https://twitter.com/RozzBozzy/status/1588661385671495680?s=20&t=wp0FRjurK-EFLGEXk8AY9w   (Eric) Vectrex Minestorm on Pico 8 (COOL) - https://www.lexaloffle.com/bbs/?tid=46482  Cody – SD Snatcher on Twitter mentioned that Yazzie on MSX has a final remastered version with many enhancments and 10 more levels.  (Tim)  - Ricki Sickenger who is one of the creators of the fantastic Rouge64 and who are now working on RogueCraft the follow up for the Amiga has posted a blog about writing Rogue64. The blog goes in to detail about how the game came about with the starter Rogue4k and developed from there. Well worth a read while we wait for RogueCraft to come out.  http://www.sickenger.com/2022/02/20/how-we-made-a-commodore-64-roguelike/  Cody – Starfox Exploration Showcase MOD - https://www.indieretronews.com/2022/11/starfox-ex-this-hack-takes-90s-hit-game.html#more  (Eric) Investigative reporting – Wrestlequest  https://wrestlingnews.co/wwe-news/jeff-jarrett-comments-on-road-doggs-current-wwe-role-his-addiction-issues-in-the-90s-wrestlequest-game-update  https://www.gematsu.com/2022/11/wrestlequest-launches-in-may-2023  Cody – Vradarks Revenge - https://zxonline.net/vradark-s-revenge-is-out/  (Tim) - Not sure if we mentioned it last month but Beamrider the great early Atari 2600 shooter from Activision has been ported to the Pico8 by Paul Hammond (@paulhamx) on twitter. A faithful and fun recreation for the Pico8 and is a free download from his Itch.io page (pahammond)  https://pahammond.itch.io/beamrider  (Eric) AQUABYSS - Eagerly awaited Amiga game by AgedCode gets an official release! - https://buff.ly/3SqpIvT #commodore #news (From Indie Retro News)    CODYS NEWS OF THE WEIRD -   https://www.nintendolife.com/news/2022/11/random-metroid-prime-devs-kept-a-gamecube-in-the-freezer-to-run-patch-code  https://www.nintendolife.com/reviews/switch-eshop/save-room  https://kotaku.com/sakuna-of-rice-and-ruin-nintendo-switch-ps4-japanese-s-1848767765  Acclaim Marketing Stunts  https://www.blockfort.com/other-lists/publicitystunts/  (Eric) Get Your Barf Bags Ready! Our new NES game Garbage Pail Kids: Mad Mike & the Quest for Stale Gum is out now on Nintendo Switch, Xbox, Playstation, Epic Games Store & Steam with the NES cartridge release to follow in a few months! http://gpkgame.com  Cody - https://www.nintendolife.com/news/2022/11/warp-drive-brings-f-zero-style-racing-with-cel-shaded-visuals-to-switch-next-month  (Eric) Xbox Series X and S can run PS2 games at 4K 60fps - https://www.gamingbible.co.uk/news/xbox-series-x-can-run-ps2-games-at-4k-60fps-20221026  (Eric) Sega Has Considered Dreamcast & Saturn Mini But Is Worried About Extreme Costs  (Eric) You Can Now Play Gameboy Games On The Steam Deck   https://retrododo.com/epilogue-gb-operator-steam-deck/  Cody – NESDEV 2022 https://itch.io/jam/nesdev-2022/entries  (Eric) Released on Nov 11th!!! - https://store.steampowered.com/app/1919470/Atari_50_The_Anniversary_Celebration/  Please give us a review on Apple Podcasts! Thanks for listening! You can always reach us at podcast@pixelgaiden.com. Send us an email if we missed anything in the show notes you need. You can now support us on Patreon.  Thank you to Henrik Ladefoged, Roy Fielding, Matthew Ackerman, Josh Malone, Daniel James, 10MARC, Eric Sandgren, Brian Arsenault, Retro Gamer Nation, Maciej Sosnowski, Paradroyd, RAM OK ROM OK, Mitsoyama, David Vincent, Ant Stiller, Mr. Toast, Jason Holland, David Motowylak, Mark Scott, Vicky Lamburn, and Paul Jacobson for making this show possible through their generous donation to the show.   Support our sponsor Retro Rewind for all of your Commodore needs! Use our page at https://retrorewind.ca/pixelgaiden and our discount code PG10 for 10%

Ian Cooper & Paul Hammond - Ultramarine - in conversation with David Eastaugh Ultramarine are an English electronic music duo, formed in 1989 by Ian Cooper and Paul Hammond. Their work blends elements of techno, house and ambient music with acoustic instrumentation, the influence of the 1970s Canterbury scene, and other eclectic sources.[1] They are best known for their 1991 album Every Man and Woman Is a Star, reissued on Rough Trade the following year.

The set of people, process, technology, and cultural norms that integrates software development and IT operations into a system-of-systems. CyberWire Glossary link: Audio reference link: "10+ Deploys Per Day: Dev and Ops Cooperation at Flickr," by John Allspaw and Paul Hammond, Velocity 09, 25 July 2009.

A software development philosophy that emphasizes incremental delivery, team collaboration, continual planning, and continual learning  Audio reference link: https://thecyberwire.com/glossary/agile-software-development "Velocity 09: John Allspaw and Paul Hammond, "10+ Deploys Pe" John Allspaw and Paul Hammond, 2009 Velocity Conference, YouTube, 25 June 2009. 

The set of people, process, technology, and cultural norms that integrates software development and IT operations into a system-of-systems. CyberWire Glossary link: https://thecyberwire.com/glossary/devops Audio reference link: "10+ Deploys Per Day: Dev and Ops Cooperation at Flickr," by John Allspaw and Paul Hammond, Velocity 09, 25 July 2009.

A software development philosophy that emphasizes incremental delivery, team collaboration, continual planning, and continual learning  CyberWire Glossary link: https://thecyberwire.com/glossary/agile-software-development Audio reference link: "Velocity 09: John Allspaw and Paul Hammond, "10+ Deploys Pe," John Allspaw and Paul Hammond, 2009 Velocity Conference, YouTube, 25 June 2009.

On this episode of the CEO Roundtable Podcast we're joined by Paul Hammond, CEO of Free Range Studios.  Free Range is a full service studio that provides branding, web development, creative and storytelling services. With everything they do, they have a great focus in the social impact space. “We work with a lot of nonprofits. We also work with for-profits. We work in the education space. We work with NGOs and government organizations who are really looking to branch out and do good in the community. It's a lot of fun. Everyone's got their own mission and we really help them tell their stories.” Paul talks about how these days, regardless of the industry you're in or if you're a brick and mortar business, everyone needs to have a digital presence and understand how to make themselves known online.  “It's so important to have a human voice as a brand and to be able to connect with people as a human people, want to connect with people and people connect to stories. It's so important that your brand has a tone, a personality that connects with, with those people in a way that they want to continue to engage with you.” Free Range Studios was founded in 1999 by Jonah Sachs and Louis Fox. They built up the creative storytelling side and carved their niche out in the nonprofit storytelling space. Paul started off as an employee and recognized some issues from mismanagement to culture over the years. After receiving his MBA from Babson with a focus on Entrepreneurship, Paul and a few partners were presented with the opportunity to take over Free Range as owners.  “Being able to really align our culture at Free Range with the goals of the nonprofits and the social organizations we work with is something that's so important. We basically saw an opportunity to say, ‘Hey, we've got these great relationships. We've got these great clients. We love the work that we're doing. Let's get Free Range back in a position where it starts to get the attention it deserves.” A now thriving company, they're building some incredible products such as an online calculator that can calculate your ecological footprint. Working for the greater good of the world and tackling some of the biggest issues that the world is facing today alongside the companies they're helping is the main priority for Paul and Free Range.  Tune into this episode of the CEO Roundtable to hear more about the global impact Free Range is helping companies move the needle on, more about Paul's own journey from employee to owner, and what it takes to reestablish a brand and culture. 

Legendary Bates College track legend, and fixture in New England Running scene for more than forty years, discusses his early days of racing and training in Maine and competing with some of New England's best runners during the height of the running boom in the early 80's.

Date recorded: November 12, 2021 Show Description: Today we welcome John Allspaw. John is an engineering leader and researcher with over 20 years of experience in building and leading teams engaged in software and systems engineering. He is a co-founder of Adaptive Capacity Labs, LLC. Previously, he was Chief Technology Officer at Etsy. He has also worked at Flickr, Friendster, InfoWorld, Salon, Genentech, Volpe National Transportation Center, and a bunch of other places as a consultant from time to time. John has spent the last decade bridging insights from Human Factors, Cognitive Systems Engineering, and Resilience Engineering to the domain of software engineering and operations. His 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. He holds a Master's degree in Human Factors and Systems Safety from Lund University. Where to find John: LinkedIn Twitter Learn more about NDM: NaturalisticDecisionMaking.org Journal of Cognitive Engineering and Decision Making Where to find hosts Brian Moon and Laura Militello: Brian's website Brian's LinkedIn Brian's Twitter Laura's website Laura's LinkedIn Laura's Twitter

John Paul Hammond (Nova York)

About JohnJohn 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 UniversityLinks: The Art of Capacity Planning: https://www.amazon.com/Art-Capacity-Planning-Scaling-Resources/dp/1491939206/ Web Operations: https://www.amazon.com/Web-Operations-Keeping-Data-Time/dp/1449377440/ The DevOps Handbook: https://www.amazon.com/DevOps-Handbook-World-Class-Reliability-Organizations/dp/1942788002/ Adaptive Capacity Labs: https://www.adaptivecapacitylabs.com John Allspaw Twitter: https://twitter.com/allspaw Richard Cook Twitter: https://twitter.com/ri_cook Dave Woods Twitter: https://twitter.com/ddwoods2 TranscriptAnnouncer: Hello, and welcome to Screaming in the Cloud with your host, Chief Cloud Economist at the Duckbill Group, Corey Quinn. This weekly show features conversations with people doing interesting work in the world of cloud, thoughtful commentary on the state of the technical world, and ridiculous titles for which Corey refuses to apologize. This is Screaming in the Cloud.Corey: Corey: This episode is sponsored in part by CircleCI. CircleCI is the leading platform for software innovation at scale. With intelligent automation and delivery tools, more than 25,000 engineering organizations worldwide—including most of the ones that you've heard of—are using CircleCI to radically reduce the time from idea to execution to—if you were Google—deprecating the entire product. Check out CircleCI and stop trying to build these things yourself from scratch, when people are solving this problem better than you are internally. I promise. To learn more, visit circleci.com.Corey: Welcome to Screaming in the Cloud. I'm Corey Quinn. I'm joined this week by John Allspaw, who's—well, he's done a lot of things. He was one of the founders of the DevOps movement—although I'm sure someone's going to argue with that—he's also written a couple of books, The Art of Capacity Planning and Web Operations and the foreword of The DevOps Handbook. But he's also been the CTO at Etsy and has gotten his Master's in Human Factors and System Safety from Lund University before it was the cool thing to do. And these days, he is the founder and principal at Adaptive Capacity Labs. John, thanks for joining me.Corey: And now for something completely different!John: Thanks for having me. I'm excited to talk with you, Corey.Corey: So, let's start at the beginning here. So, what is Adaptive Capacity Labs? It sounds like an experiment in auto-scaling, as is every use of auto-scaling, but that's neither here nor there. I'm guessing it goes deeper.John: Yeah. So, I managed to trick, or let's say convince some of my heroes, Dr. Richard Cook and Dr. David Woods, these folks are what you would call heavies in the human factors, system safety, and resilience engineering world, Dave Woods is credited with creating the field of resilience engineering. And so what we've been doing for the past—since I left Etsy is bringing perspectives, techniques, approaches to the software world that are, I guess, some of the most progressive practices that saved other safety, critical domains, like aviation, and power plants, and all of the stuff that makes news.And the way we've been doing that is largely through the lens of incidents. And so we do a whole bunch of different things, but that's the core of what we do is activities and projects for clients that have a concern around incidents; both, are we learning well? Can you tell us that? Or can you tell us how to understand incidents and analyze them in such a way that we can learn from them effectively?Corey: Generally speaking, my naive guess, based upon the times I spent working in various operations role has been, “Great. So, how do we learn from incidents?” Well, if you're like most of the industry, you really don't. You wind up blaming someone in a meeting that's called blameless, so instead of using the person's name, you use a team or a role name, and then you wind up effectively doing a whole bunch of reactive process work that in long enough timeline and enough incidents ossifies you into a whole bunch of processes and procedure that is just horrible. And then how do you learn from this?Well, by the time it actually becomes a problem, you've rotated CIOs four times and there's no real institutional memory here. Great. That's my cynical approach, and I suspect it's not entirely yours because if it were, you wouldn't be doing a business in this because otherwise, it would be this wonderful choreographed song-and-dance number of, “Doesn't it suck to be you? Da-da.” And that's it. I suspect you do more as a consultant than that. So, what does my lived experience of terrible companies differing in what respects from the folks you talk to?John: Oh, well, I mean, just to be blunt, you're absolutely spot on. [laugh]. The industry is terrible at this.Corey: Well, crap.John: I mean, look, the good news is, there are inklings, there are signals for some organizations that have been doing the things that they've been told to do by some book or website that they read, and they're doing all the things and they realize, “All right, well, whatever we're doing doesn't seem to be—it doesn't feel—we're doing all the things, checking the boxes, but we're having incidents”—and even more disturbing to them is we're having incidents that seem as if—it'd be one thing to have incidents that were really difficult, hairy, complicated, and complex, and certainly those happen, but there is a view that they're just simply not getting as much out of these sometimes pretty traumatic events as they could be. And that's all that's needed, yeah.Corey: In most companies, it seems like, on some level, you're dealing with every incident that looks a lot like that. Sure, it was a certificate expired, but then you wind up tying into all the relevant things that are touching that. It seems like it's an easy, logical conclusion. Oh, wow. It turns out in big enterprises, nothing is straightforward or simple.Everything becomes complicated, and issues like that happen frequently enough that it seems like the entire career can be spent in pure firefighting reactive mode.John: Yeah, absolutely. And again, I would say that just like these other domains that I mentioned earlier, there's a lot of, sort of, intuitive perspectives that are, let's just say, sort of unproductive. And so in software, we write software; it makes sense if all of our discussions after an incident trying to make sense of it, is entirely focused on the software did this, and Postgres has this weird thing, and Kafka has this tricky bit here. But the fact of the matter is, people and—engineers and non-engineers—are struggling when an incident arises, both in terms of what the hell is happening, and generating hypotheses, and working through whether the hypothesis is valid or not, adjusting it if signals show up that it's not, and what can we do, what are some options? If we do feel like we're on a good [unintelligible 00:06:09] productive thread about what's happening, what are some options that we can take?That opens up a doorway for a whole variation of other questions. But the fact of the matter is, handling incidents, understanding really, effectively, time-pressured problem solving, almost always amongst multiple people with different views, different expertise, and piecing together across that group what's happening, and what to do about it, and what are the ramifications of doing this thing versus that thing? This is all what we would call above-the-line work. This is expertise. It shows up in how people weigh ambiguities, and things are uncertain.And that doesn't get this lived experience that people have, it just we're not used to talking about—we're used to talking about networks, and applications, and code, and network. We're not used to talking about and even have vocabulary for what makes something confusing? What makes something ambiguous? And that is what makes for effective incident analysis.Corey: Do you find that most of the people who are confused about these things tend to be more aligned with being individual contributor type engineers, who are effectively boots-on-the-ground, for lack of a better term? Is it high-level executives who are trying to understand why it seems like they're constantly getting paraded in the press? Or is it often folks somewhere between the two?John: Yes.Corey: [laugh].John: Right? Like there is something that you point out, which is this contrast between boots-on-the-ground, hands-on keyboard, folks who are resolving incidents, who are wrestling with these problems, and leadership. And sometimes leadership who remember their glory days of being an individual contributor sometimes are a bit miscalibrated. They still believe they have a sufficient understanding of all the messy details when they don't. And so, I mean, the fact of the matter is, there's the age-old story of Timmy stuck in a well, right?There's the people trying to get Timmy out of the well, and then there's what to do about all of the news reporters surrounding the well asking for updates and questions, and how did Timmy get in the well? These are two different activities. And I'll tell you pretty confidently, if you get Timmy out of the well, pretty fluidly, if you can set situations up where people who ostensibly would get Timmy out of the well are better prepared with anticipating Timmy is going to be in the well, and understanding all the various options and tools to get Timmy out of the well, the more you can set up those and have those conditions be in place, there's a whole host of other problems that simply don't go away. And so, these things kind of get a bit muddled. And so when you say ‘learning from incidents,' I would separate that very much from what you tell the world externally from your company about the incident because they're not at all the same.Public write-ups about an incident are not the results of an analysis. It's not the same as an internal review, were the review to be effective. Why? Well, first thing is you never see apologies on internal post-incident reviews because who are you going to apologize to?Corey: It's always fun watching the certain level of escalating transparency as you go up through the spectrum of the public explanation of an outage, to ones you put internal customers, to ones you show under NDA to special customers, to the ones who are basically partners who are going to fire you contractually if you don't, to the actual internal discussion about it. And watching that play out is really interesting. As you wind up seeing the things that are buried deeper and deeper, yeah, you wind up with this flowery language on the outside, and it gets more and more transparent, and at the end, it's, “Someone tripped and hit the emergency power switch in a data center.” And it's this great list of how this stuff works.John: Yeah. And to be honest, it would be strange and shocking if they weren't different. Because like I said, the purpose of a public write-up is entirely different than an internal write-up and the audience is entirely different. And so that's why they're cherry-picked. There's a whole bunch of things that aren't included in public write-up because the purpose is, “I want a customer or potential customer to read this and feel at least a little bit better.”Or really, I want them to at least get this notion that we've got a handle on it. “Wow, that was really bad, but nothing to see here, folks. It's all been taken care of.” But again, this is very different, the people inside the organization, even if it's just sort of tacit, they've got a knowledge. Tenured people who have been there for some time, see connections, even if they're not made explicit, between one incident to another incident.To that one that happened—“Remember that one that happened three years ago, that big one? Oh, sorry, you're new. Oh, let me tell you the story. Oh, it's about this and blah, blah, blah. And who knew that Unix pipes only passes 4k across it.” Blah, blah, blah, something—some weird, esoteric thing.And so our focus, largely, although we have done projects with companies about trying to be better about their external language about it, the vast majority of what we do and where our focuses is, is to capture the richest understanding of an incident for the broadest audience. And like I said at the very beginning, the bar is real low. There's a lot of, I don't want to say falsehoods, but certainly a lot of myths that just don't play out in the data about whether people are learning. Whenever we have a call with a potential client, we always ask the same question. Ask them about what their post-incident activities look like, and they tell us and throw in some cliches, and everyone—never want a crisis go to waste.And, “Oh, yes. And we always try to capture the learnings and we put them in a document.” And we always ask the same question, which is, “Oh. So, you put these documents, these write-ups in an area?” Oh, yes, we want that to be shared as much as possible.And then we say, “Who reads them?” And that tends to put a bit of a pause because most people have no idea whether they're being read or not. And the fact is, when we look, very few of these write-ups are being read. Why? I'll be blunt: because they're terrible. [laugh].There's not much to learn from there because they're not written to be read. They're written to be filed. And so we're looking to change that. And there's a whole bunch of other things that are unintuitive, but just like all of the perspective shifts, DevOps, and continuous deployment, they sound obvious, but only in hindsight after you get it. That's characterization of our work.Corey: It's easy to wind up, from the outside, seeing a scenario where things go super well in an environment like that, where, okay, we brought you in as a consultant, suddenly, we have better understanding about our outages. Awesome. But outages still happen. And it's easy to take a cynical view of, okay, so other than talking to you a lot, we say the right things, but how do we know that companies are actually learning from what happened as opposed to just being able to tell better stories about pretending to learn?John: Yeah, yeah. And this is, I think, where the world of software has some advantages over other domains. And the fact is, software engineers don't pay any attention to anything they don't think the attention is warranted, or they're not being judged, or scored, or rewarded for. And so there's no single signal that accompanies learning from incidents. It's more like a constellation, like, a bunch of smaller signals.So, for example, if more people are reading the write-ups. If more people are attending group review meetings. In organizations that do this really well, engineers who start attending meetings, we ask them, “Well, why are you going to this meeting?” And they'll report, “Well, because I can learn stuff here that I can't learn anywhere else. Can't read about it in a runbook, can't read about it on the wiki, can't read about it in an email, or hear about it in an all-hands.”And that they can see a connection between, even incidents handled in some distant group, they can see a connection to their own work. And so those are the sort of signals—we've written about this on our blog—those are the sort of signals that we know that progress is building momentum. But a big part of that is capturing this, again, this experience. Usually, we'll see, there's a timeline, and this is when memcached did X, and this alert happened, and then blah, blah, blah, blah, blah. Right?But very rarely are captured the things that, when you ask an engineer, “Tell me your favorite incident story.” People who will even describe themselves, “Oh, I'm not really a storyteller, but listen to this.” And they'll include parts that make for a good story. Social construct is, if you're going to tell a story, you've got the attention of other people, you're going to include the stuff that was not usually kept or captured in write-ups. For example, like, what was confusing?A story that tells about what was confusing, well—“And then we looked, and it said, ‘zero tests failed.'”—this is an actual case that we looked at—“It says ‘zero tests failed.' And so, okay. So, then I deployed. Well, the site went down.” “Okay, well, so what's the story there?” “Well, listen to this. As it turns out, at a fixed font, zeros, like, in Courier or whatever, have a slash through it and at a small enough font, a zero with a slash through it looks a lot like an eight. There were eight tests failed, not zero.” So, that's about the display. And so those are the types of things that make a good story. We all know stories like this, right? The Norway problem with YAML. You ever heard of that Norway problem?Corey: Not exactly. I'm hoping you'll tell me.John: Well, so lay [laugh] it's excellent, and of course it works out that the spec for YAML will evaluate the value no—N-O—to false as if it was a boolean. Yes, for true. Well, but if your YAML contains a list of abbreviations for countries, then you might have Ireland, Great Britain, Spain, US, false instead of Norway. And so that's just an unintuitive surprise. And so, those are the types of things that don't typically get captured in incident writeups.There might be a sentence like, “There was a lack of understanding.” Well, that's unhelpful. At best. Don't tell me what wasn't there. Tell me what was there. “There was confusion.” Great. “What made it confusing?” “Oh, yeah. N-O is both ‘no' and the abbreviation for Norway.”Red herrings is another great example. Red herrings happen a lot; they tend to stick in people's memories; and yet, they never really get captured. But it's, like, one of the most salient aspects of the case that ought to be captured. People don't follow red herrings because they know they're a red herring. They follow red herrings because they think it's going to be productive.So therefore, you better describe for all your colleagues what brought you to believe that this was productive. Turns out later—you find out later that it wasn't productive. Those are some of the examples. And so if you can capture what's difficult, what's ambiguous, what's uncertain, and what made it difficult, ambiguous, or uncertain, that makes for good stories. If you can enrich these documents, it means people who maybe don't even work there yet, when they start working there, they'll be interested; they have a set expectation they'll learn something by reading these things.Corey: This episode is sponsored by our friends at Oracle Cloud. Counting the pennies, but still dreaming of deploying apps instead of "Hello, World" demos? Allow me to introduce you to Oracle's Always Free tier. It provides over 20 free services and infrastructure, networking databases, observability, management, and security.And - let me be clear here - it's actually free. There's no surprise billing until you intentionally and proactively upgrade your account. This means you can provision a virtual machine instance or spin up an autonomous database that manages itself all while gaining the networking load, balancing and storage resources that somehow never quite make it into most free tiers needed to support the application that you want to build.With Always Free you can do things like run small scale applications, or do proof of concept testing without spending a dime. You know that I always like to put asterisks next to the word free. This is actually free. No asterisk. Start now. Visit https://snark.cloud/oci-free that's https://snark.cloud/oci-free.Corey: There's an inherent cynicism around… well, from at least from my side of the world, around any third-party that claims to fundamentally shift significant aspects of company culture, and if the counter-argument to that is that you and DORA and a whole bunch of other folks have had significant success with doing it, it's just very hard to see that from the outside. So, I'm curious as to how you wind up telling stories about that because the problem is inherently whenever you have an outsider coming into an enterprise-style environment, is, “Oh, cool. What are they going to be able to change?” And it's hard to articulate that value, and not—well, given what you do, to be direct—come across as an engineering apologist, where it's well, “Engineers are just misunderstood, so they need empathy, and psychological safety, and blameless post-mortems.” And it sounds to crappy executives, if I'm being direct, that, “Oh, in other words, I just can't ever do anything negative to engineers who, from my perspective, just failed me or are invisible, and there's nothing else in my relationship with them.” Or am I oversimplifying?John: No, no. I actually think you're spot on. I mean, that's the thing is that if you're talking with leaders—remember, a.k.a. People who are, even though they're tasked with providing the resources and setting conditions for practitioners—the hands-on folks who get their work done—they're quite happy to talk about these sort of abstract concepts, like psychological safety and insert other sorts of hand-wavy stuff.What is actually pretty magical about incidents is that these are grounded, concrete, messy phenomena that practitioners have, and will remember; they're sometimes visceral experiences. And so that's why we don't do theory at Adaptive Capacity Labs. We understand the theory, happy to talk to you about it, but it doesn't mean as much without the practicality. And the fact of the matter is that the engineer apologist is, “If you didn't have the engineers, would you have a business?” That's at the flip side; this is, like, the core unintuitive part of the field of resilience engineering, which is that Murphy's Law is wrong.What could go wrong almost never does, but we don't pay much attention to that. And the reason why you're not having nearly as many incidents as you could be is because, despite the fact that you make it hard to learn from incidents, people are actually learning. But they're just learning out of view from leaders. When we go to an organization and we see that most of the people who are attending post-incident review meetings are managers, that has a very particular signal. That tells me that the real post-incident review is happening outside that meeting, it probably happened before that meeting, and those people are there to make sure that whatever group that they represent in their organization isn't unnecessarily given the brunt of the bottom of a bus.And so it's a political due diligence. But the notion that you shouldn't punish or be harsh on engineers for making mistakes completely misses the point. The point is to set up the conditions so that engineers can understand the work that they do. And if you can amplify that, as Andrew Schaffer has said, “You're either building a learning organization, or you're losing to someone who is.” And a big part of that is you need people; you have to set up conditions for people to give detailed story about their work, what's hard.This part of the codebase is really scary, right? All engineers have these notions: this part is really scary, this part is really not that big of a deal, this part is somewhere in between. But there's no place for that outside of the informal discussions. But I would assert that if you can capture that, the organization will be better prepared. The thing that I would end on that is that it's a bit of a rhetorical device to get this across, but one of the questions we'll ask is, “How can you tell the difference between a difficult case—a difficult incident—handled well, or a straightforward incident handled poorly?”Corey: And from the outside, it's very hard to tell the difference.John: Oh, yeah. Well, certainly if what you're doing is averaging how long these things take. But the fact of the matter is that all the people who were involved in that, they know the difference between a difficult case handled well, and a straightforward one handled poorly. They know it, but there's nowhere, there's no place to give voice to that lived experience.Corey: So, on the whole, what is the tech industry missing when it comes to learning effectively from the incidents that we all continually experience and what feels to be far too frequently?John: They're missing what is captured in that age-old parable of the blind men and the elephant. And I would assert that these blind men that the king sends out—“Go find an elephant and come back and tell me about the elephant”—they come back and they all have—they're all valid perspectives, and they argue about, “No, an elephant is this big flexible thing,” and other one is, “Oh, no, an elephant is this big wall,” and, “No, an elephant is a big flappy thing.” If you were to make a synthesis of their different perspectives, then you'd have a richer picture and understanding of an elephant. You cannot legislate—and this is where what you brought up—you cannot set ahead, a priori, some amount of time and effort. And quite often what we see are leaders saying, “Okay, we need to have some sort of root cause analysis done within 72 hours of an event.” Well, if your goal is to find gaps, and come up with remediation items, that's what you're going to get. Remediation items might actually not be that good because you've basically contained the analysis time.Corey: Which does sort of feel, on some level, like it's very much aligned as—from a viewpoint of, yeah, remediation items may not be useful as far as driving lasting change, but without remediation items, good luck explaining to your customers that will never ever, ever happen again.John: Right, yeah. Of course. Well, you'll notice something about those public write-ups; you'll notice that they don't tend to link to previous incidents that have similarities to them because that would undermine the whole purpose, which is to provide confidence. And a reader might actually follow a hyperlink to say, “Wait a minute. You said this wouldn't happen again.”Turns out it would. Of course, that's horseshit. But you're right. And there's nothing wrong with remediation items, but if that's the goal, then that goal is—you know, what you look for is what you find, and what you find is what you fix. If I said, “Here's this really complicated problem and I'm only giving you an hour to describe it,” and it took you eight hours to figure out the solution.Well then, what you come up with in an hour is not actually going to be all that good. So, then the question is, how good are the remediation items? Quite often what we see is—and I'm sure you've had this experience—an incident's been resolved and you and your colleagues are like, “Wow, that was a huge pain in the ass. Oh, dude. I didn't see that coming. That was weird. Yeah.” And one of you might say, “You know what? I'm just going to make this change because I don't want to be woken up tonight, or I know that making this change is going to help things. I'm not waiting for the post-mortem. We're just going to do that.” “Is that good?” “Yep.” “Okay, yeah, please do it.”Quite frequently, those things, those actions, those aren't listed as action items, and yet it was a thing so important that it couldn't wait for the post-mortem—arguably the most important action item—and it doesn't get captured that way. We've seen this take place. And so again, in the end, it's about those who have the lived experience. The live experience is what fuels how reliable you are today.You don't go to your senior technical people and say, “Hey, listen. We got to do this project. We don't know how. I want you to figure out—we're going to—let's say we're going to move away from this legacy thing, so I want you to get in a room, come up with two or three options. Gather a group of folks who know what they're talking about. Get some options, and then show me what the options. Oh, and by the way, I'm prohibiting you from taking into account any experience you've ever had with incidents.” It sounds ridiculous when you would say that, and yet, that is what [unintelligible 00:27:54].So, if you can fuel people's memory, you can't say you've learned something if you can't remember it. At least that's what my kids' teachers tell me. And so yeah, you have to capture the lived experience, and including what was hard for people to understand. And those make for good stories. That makes for people reading them. That makes for people to have better questions about it. That's what learning looks like.Corey: If people want to learn more about what you have to say and how you view these things, where can they find you?John: You can find me and my colleagues at adaptivecapacitylabs.com where we talk all about the stuff on our blog. And myself, and Richard Cook, and Dave Woods are also on Twitter, as well.Corey: And we'll, of course, include links to that in the [show notes 00:28:42]. John, thank you so much for taking the time to speak with me today. I really appreciate it.John: Yeah, thanks. Thanks for having me. I'm honored.Corey: John Allspaw, co-founder and principal at Adaptive Capacity Labs. I'm Cloud Economist Corey Quinn, and this is Screaming in the Cloud. If you've enjoyed this podcast, please leave a five-star review on your podcast platform of choice, whereas if you hated this podcast, please leave a five-star review on your podcast platform of choice, along with a comment giving me a list of suggested remediation actions that I can take to make sure it never happens again.Corey: If your AWS bill keeps rising and your blood pressure is doing the same, then you need the Duckbill Group. We help companies fix their AWS bill by making it smaller and less horrifying. The Duckbill Group works for you, not AWS. We tailor recommendations to your business and we get to the point. Visit duckbillgroup.com to get started.Announcer: This has been a HumblePod production. Stay humble.

Paul is one of the wisest men I have ever met. With almost 88 years of experience on this earth, he is a wealth of knowledge. I was grateful to have the opportunity to sit down with such a man. 

PAUL HAMMOND-Lead guitar- GET THE LED OUT (also plays the Theremin on Whole Lotta Love) Coming to THE NORTHLANDS - Sat July 31st (Sold Out Casino show 8/28).

Sean Rollason known as ROLLO to many was my first dressing room and digs buddy in Pantomime, it was during my first panto and days after it ending we flew off to Benidorm to open in a Nightclub performing our acts to stag and hen parties amongst Blue comics and strippers. If you think that was a contrast then you'll love the next hour or so.Sean got the circus bug and his knowledge and talent outshine many as he talks us through his experiences in the business from Death defying elephant stunts to performing Pantomime in a Pandemic. His relationship with his son and daughter Tommy J & Lucy is a wonderful thing, he is the supportive father as Michelle is the supportive mother but they are all clearly best friends too. They are great great people.We laugh and get serious about showbusiness as well as talk of our passion as members of www.gowr.net.Welcome to Eyes & Teeth ROLLO

The Queen's Speech to Parliament in May 2021 announced plans to bring forward legislation to ban “conversion therapy”. Though there are many practices evangelical Christians should rightly reject as abhorrent, there is also a real threat to ordinary gospel ministry. In this episode, you'll hear FIEC National Director John Stevens speaking to Paul Hammond on UCB's Friday Round Up (recorded 19 March 2021) about the proposed ban to "conversion therapy". For a written, biblical response to conversion therapy, visit the FIEC website.

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.

Paul is widely recognized as an industry leader in the use and deployment of working dog teams, with a distinguished career spanning 30+ years, having managed many of the world's largest operational canine programs. He has vast experience in domestic & international terrorism, spanning 20 years of continuous K9 deployments in hostile environments, including Iraq, Afghanistan & Northern Ireland in support of the U.S. Dept. of Defense, U.S. Dept. of State, the British Military & Private Security Sector. Paul has served as the senior working-dog advisor for multiple Military Defense, Research, and Evaluation agencies. He has also worked alongside Auburn University's Canine Performance Science Program on key Government research initiatives. 360 K0 Group Website: https://360k9group.com/ U.S Canine Biathlon Website: https://uscaninebiathlon.com/ Join the Dogs & Deadlifts Community:https://dogsanddeadlifts.mykajabi.com/

First, Michael Cymbor, OD, FAAO, and Nicole Stout, OD, FAAO, walk through the steps of what to do once a patient is identified as a glaucoma suspect, then Paul Hammond, OD, FAAO, provides a rundown of the latest trends in glaucoma diagnosis and treatment. Next, Aaron McNulty, OD, FAAO, discusses the changing role of laser in the management of patients with open-angle glaucoma, and Matthew D. Bovenzi, OD, FAAO, Dipl(ABO), closes the episode with his article on adjunctive therapy for patients with glaucoma, specifically when it makes sense to consider adding a second drop.  

The awesome @paullistensto Paul Hammond joined Steve in hmv Head Office to collate his Fantasy Festival as we caught up for the first time in 2 years to talk music, music, music aswell as live experiences, hmv & lots more... If you've enjoyed the Fantastival Podcast please give us a follow on Twitter @FantastivalP and remember to check for our new episodes which are released every Sunday at 9am. Spread the word... and the word is Fantastival! --- Send in a voice message: https://anchor.fm/the-fantastival-podcast/message

Chief Financial Officer & Principal at Nexus PMG. Responsible for financial strategy, governance & compliance. Dedicated to delivering world-class services for our clients in the lending & investing communities and owner/developer teams. Chartered Global Management Accountant with a successful track record of applying industry-leading standards to create operational and management efficiencies that optimize strategic decision making. Previous roles include Business Services Manager for Fluor, overseeing Accounting and Finance project teams in the Energy & Chemicals and Mining & Metals industries. Led Project Business Services teams in Europe and the Middle East on megaprojects and programs valued up to $11 billion. https://nexuspmg.com/

This was part of my COVID 19 lecture series for the spring of 2020 courses that I taught. I had the oppurtunity to talk with my friend and colleage Paul Hammond II about machine learning, digital culture, and what it all means. Deep! This was for my...

Welcome back to the third episode of Couture & Construction, an uplifting podcast dedicated to the many different aspects of the luxury building industry. On today's episode we talk to luxury builder and Hammond & Brandt business owner, Paul Hammond! He breaks down one of the most important pieces of the building process: budgets. This is the first part of a two part series that we are doing regarding budgeting your build.

All Access talks with multi-talented guitarist Paul Hammond from Get The Led Out! Paul shares how the band prepares their tours, how his long hair helped score him a spot in the band, and his impressive guitar collection. See Get The Led Out live on February 21. For more information: https://www.stnj.org/event/get_the_led_out

To eat or not to eat? That's the question Paul Hammond asks guest David Clough, especially when it comes to meat and how we treat animals.

In this episode of HITS Radio, HITS instructor Paul Hammond discusses the classes he will be teaching at HITS and shares some great training tips to make any bomb dog team better. For more information about HITS and to see Paul's bio, check out our web-page, www.HITSK9.net To contact the host, Jeff Meyer, email Jeff@HITSK9.net

In this episode of HITS Radio, HITS instructor Paul Hammond discusses the classes he will be teaching at HITS and shares some great training tips to make any bomb dog team better. For more information about HITS and to see Paul's bio, check out our web-page, HITSK9.net To contact the host, Jeff Meyer, email Jeff@HITSK9.net

Tweet Paul Hammond, guitarist in Get the Led Out, aka “The American Led Zeppelin,” performs some of his favorite Zep songs, talks about the challenges of delivering this music night after night, and teaches David “Black Dog” on the spot. The post In The Pocket – Episode 36 – Paul Hammond appeared first on Wildfire Radio.

How many men do you know who have ran TOWARDS over a thousand explosive devices AND handled a leash for damn near three decades? If you handle an Explosive Detection Dog DO NOT MISS THIS EPISODE. Paul of Vapor Wake talks to the guys about the importance of intelligence gathering for EDD Handlers. He then explains in great detail the difference between traditional EDD's, Crowd Screening and Mass Screening EDD. We were lucky enough to attend the VERY FIRST K9 Biathlon they hosted on their Anniston AL compound with several hundred people and Paul talks about how it is now attended by over a THOUSAND runners plus vendors, music, food and of course beer!! Thank you Paul! To see what Paul and the Vapor Wake Team do- visit them at https://homeofvaporwake.com/ and sign up for the Biathlon HERE: https://www.adventuresignup.com/Race/AL/Anniston/USCanineBiathlon A HUGE continued thank you to our sponsors: HITS K9 Training and Conference https://www.hitsk9.net or Jeff Barrett at 863-529-5113 US-K9 Rad tugs and reward toys!! (USE DISCOUNT CODE K9PRO) www.usa-K9.com Ray Allen Manufacturing https://www.rayallen.com (USE DISCOUNT CODE WorkingDogRadio FOR 10% OFF your next order) Dogtra (Use Discount Code WDR10 for 10% a single item over $200) www.dogtra.com QuickDerm by Vet Care Fast Acting Wound Care for all species of animal! Use Code: 10WDR For 10% off your first order!! www.vetcare.us Tactical Police K9 Training at https://www.tacticalpolicek9training.com EMPLOYMENT OPPORTUNITY: Coast 2 Coast K9 www.c2ck9.com Silver State K9 https://www.SilverStateK9.com or on Facebook and Instagram @silverstatek9 Southern Coast K9 at https://www.southerncoastk9.com or 877.903.DOGS True Scent K9 Training Aids available HERE: https://www.truescentk9.com or 512-533-2040 Discount Code WDR15 for 15% off training aids excluding accessories ALM Suits & K9 Equipment https://www.almk9equipment.com (Ise Discount Code WDRADIO for 10% off your first order) Tripwire Operations Group https://www.tripwireops.org Music with permission By Brother Dege – Official www.brotherdege.blogspot.com, on itunes, Amazon, CD Baby or anywhere you stream digital media Edited and co-produced by Alesha Brandt

How many men do you know who have ran TOWARDS over a thousand explosive devices AND handled a leash for damn near three decades? If you handle an Explosive Detection Dog DO NOT MISS THIS EPISODE. Paul of Vapor Wake talks to the guys about the importance of intelligence gathering for EDD Handlers. He then explains in great detail the difference between traditional EDD’s, Crowd Screening and Mass Screening EDD. We were lucky enough to attend the VERY FIRST K9 Biathlon they hosted on their Anniston AL compound with several hundred people and Paul talks about how it is now attended by over a THOUSAND runners plus vendors, music, food and of course beer!! Thank you Paul! To see what Paul and the Vapor Wake Team do- visit them at https://homeofvaporwake.com/ and sign up for the Biathlon HERE: https://www.adventuresignup.com/Race/AL/Anniston/USCanineBiathlon A HUGE continued thank you to our sponsors: HITS K9 Training and Conference https://www.hitsk9.net or Jeff Barrett at 863-529-5113 US-K9 Rad tugs and reward toys!! (USE DISCOUNT CODE K9PRO) www.usa-K9.com Ray Allen Manufacturing https://www.rayallen.com (USE DISCOUNT CODE WorkingDogRadio FOR 10% OFF your next order) Dogtra (Use Discount Code WDR10 for 10% a single item over $200) www.dogtra.com QuickDerm by Vet Care Fast Acting Wound Care for all species of animal! Use Code: 10WDR For 10% off your first order!! www.vetcare.us Tactical Police K9 Training at https://www.tacticalpolicek9training.com EMPLOYMENT OPPORTUNITY: Coast 2 Coast K9 www.c2ck9.com Silver State K9 https://www.SilverStateK9.com or on Facebook and Instagram @silverstatek9 Southern Coast K9 at https://www.southerncoastk9.com or 877.903.DOGS True Scent K9 Training Aids available HERE: https://www.truescentk9.com or 512-533-2040 Discount Code WDR15 for 15% off training aids excluding accessories ALM Suits & K9 Equipment https://www.almk9equipment.com (Ise Discount Code WDRADIO for 10% off your first order) Tripwire Operations Group https://www.tripwireops.org Music with permission By Brother Dege – Official www.brotherdege.blogspot.com, on itunes, Amazon, CD Baby or anywhere you stream digital media Edited and co-produced by Alesha Brandt

Paul Hammond has worked all over the world combatting domestic and international terrorism and training K9s to serve alongside their military and private security handlers as indispensable assets in that fight Paul talks with Marcie and Lovey about the principled training these dogs and their handlers receive, the K9s acute olfactory abilities and how they are used to detect body-worn explosives on a moving target. These multi-disciplined K9 teams are trained to be deployed in settings ranging from concert venues to airports throughout the world. Paul also discusses their innovative partnership with Auburn University and their ability to breed these high-performing K9s. EPISODE NOTES: Making the World a Safer Place with Marcie Davis

In this podcast recorded at the Agile 2018 conference Shane Hastie, Lead Editor for Culture & Methods, spoke to Phil Brock and Paul Hammond of the Agile Alliance about the current state of the Alliance and plans for the future. Why listen to this podcast: • Agile 2018 had around 2400 attendees, from 54 countries and 900 companies, with over 270 sessions across the five days of the conference • The Agile Alliance initiatives represent the areas that the Alliance is involved in and supporting their members globally • The mission of the alliance is to create an inclusive global community, advance the breadth and depth of agile and provide value to the member community • Affiliates are being established where there is a strong community that wants to come together and have a more local focus with support that is appropriate for the local context Being a part of the agile community implies that one is participating, not simply consuming More on this: Quick scan our curated show notes on InfoQ https://bit.ly/2A5TrEW You can also subscribe to the InfoQ newsletter to receive weekly updates on the hottest topics from professional software development. bit.ly/24x3IVq Subscribe: www.youtube.com/infoq Like InfoQ on Facebook: bit.ly/2jmlyG8 Follow on Twitter: twitter.com/InfoQ Follow on LinkedIn: www.linkedin.com/company/infoq Check the landing page on InfoQ: https://bit.ly/2A5TrEW

When you think of the annual Agile conference, you usually think about speakers and content. However, Paul Hammond wants to augment the content at the conference with the answers to your questions and one-on-one time with experts from around the industry. That’s why, this year, the conference includes Agile Therapy. Learn more in this video with Paul and Chris Li.

In this podcast, Jessie Shternshus , Paul Hammond and I take a shot at addressing the question of whether organizations have become so focused by the need to “do” Agile that they may have lost the ability to actually “be” Agile. During the conversation we touch on a number of the key challenges organizations are facing and how these challenges are impacting individuals at the team level. Show Notes 00:45 Introduction to Jessie and Paul 02:00 The Topic(s): Do we need to return to a more simple version of it so that people can better understand/internalize the fundamental intent behind it and not simply get lost in dogma and going thru the motions? How do we help “them” figure out the “why”? 06:30 Does leadership need to deeply understand Agile to help support transition to Agile or can the organization succeed if they just want to “do Agile”? 08:48 Changing the conversation to help people approach Agile with a more open mindset? 10:48 Mapping organizational values to Agile Manifesto values 11:30 How to create hope (that things can improve) at an organization? 14:20 Taking the option to “Make a choice” 16:37 Advice for getting “Buy In” 18:03 How do we unfreeze the frozen middle? 20:08 Should leadership demonstrate vulnerability when trying to transition to Agile? (crickets) 20:46 How do I help my company become a place innovative, agile people will want to work? 22:47 You can’t put a band-aid on culture 23:56 What id you hire for the culture you want, and disappoint the new folks with what you have? 26:15 Has anyone’s Agile transformation ever gone fast enough? What is the pace of transition that you need? 27:17 Remember to acknowledge the positives 28:00 Advice for Senior Mgmt. on adopting Agile 32:36 Advice for Team Members who feel like Mgmt. doesn’t get it yet 36:30 How to reach Jessie and Paul 38:29 Close Contacting Jessie and Paul Jessie is the founder of The ImprovEffect. You can reach her at her site here: http://www.improveffect.com or via Twitter: https://twitter.com/TheImprovEffect. She also has a number of upcoming events which can be found here: http://www.improveffect.com/events/ Paul Hammond is is the Director European Product Development at eBay and can be reached via his website: http://phammond.com or on Twitter: https://twitter.com/phammond. Paul is also on the Board of the Agile Alliance. You can find more about the upcoming Agile Alliance Technical Conference here: https://www.agilealliance.org/agile-alliance-technical-conference-2017/

This is the Engineering Culture Podcast, from the people behind InfoQ.com and the QCon conferences. In this podcast, Shane Hastie, InfoQ Lead Editor for Culture & Methods, talks to Phil Brock, Rebecca Parsons, Paul Hammond and Victor Hugo about the state of the Agile Alliance, new initiatives being worked on around the world and the future of agility in the workplace. Why listen to this podcast: - The Agile 2016 conference was the largest ever with nearly 2500 people attending - The Agile Alliance is spreading around the world with events and through affiliates - The Agile Alliance has responded to the criticism about the main conference having less technical content and ran a Technical Conference in 2016 with another scheduled for 2017, as well as having technically focused initiatives which are exploring new technical practices in response to the changing technical landscape - Member driven initiatives are receiving more focus and more funding to engage the agile community The Agile Alliance website has a large repository of content which is freely available to the global agile community, and more is constantly being produced Notes and links can be found on InfoQ: http://bit.ly/2dDB01f - 4m 55s The Agile Alliance is spreading into parts of the world beyond North America with affiliates and with events in different countries. - 5m 05s Victor talks about the Agile Europe and Agile Brazil conferences. - 6m 09s The value of having an Affiliate in Brazil is about providing a structure and support for the large Agile Brazil conference as well as providing a vehicle to support the growth of a healthy agile community in Brazil - 7m 25s There are a variety of Initiatives which the Alliance supports. These are ways for the community to get involved and to propose ideas for areas they want to see the Alliance working in. There are three types of initiatives the Alliance supports More on this: Quick scan our curated show notes on InfoQ. http://bit.ly/2dDB01f You can also subscribe to the InfoQ newsletter to receive weekly updates on the hottest topics from professional software development. http://bit.ly/2cMnjfW

Dan Attfield and Paul Hammond discovered that the rules of improv comedy are the polar opposite of Patrick Lencioni's "Five Dysfunctions of a Team."  For example, the first dysfunction is Absense of Trust, but in an effective team, you encourage the Presence of Trust. The duo walked Agile Amped through a series of exercises that they used in their session "The Five Dysfunctions of an Improvised Comedy Group"--which started out right with a blackout disco with Beyonce blaring on the speakers. In the end, Dan and Paul have one goal: getting people to change their egocentric views to one that focuses on making others look awesome. Mandy Ross from Sococo, SolutionsIQ partner, hosts at Agile2016 in Atlanta, GA. About Agile Amped The Agile Amped podcast series connects the community through compelling stories, passionate people, shared knowledge, and innovative ideas. Fueled by inspiring conversations with industry thoughtleaders, Agile Amped offers valuable content – anytime, anywhere. To receive real-time updates, subscribe at YouTube, iTunes or SolutionsIQ.com. Subscribe: http://bit.ly/SIQYouTube, http://bit.ly/SIQiTunes, http://www.solutionsiq.com/agile-amped/ Follow: http://bit.ly/SIQTwitter  Like: http://bit.ly/SIQFacebook

Crime Club. January 22, 1947. Mutual net. "Mr. Smith's Hat". Sustaining. A man calls the police to say he's going to be murdered. Ten seconds later, the man's daughter calls to say she just found the body. Roger Bower (producer, director), Elaine Kent, Raymond Edward Johnson, William Podmore, Eleanor Phelps, Paul Hammond, Shirling Oliver, Barry Thompson, Helen Riley (author), Stedman Coles (adaptor). oldtimeradiodvd.com

Crime Club. January 22, 1947. Mutual net. "Mr. Smith's Hat". Sustaining. A man calls the police to say he's going to be murdered. Ten seconds later, the man's daughter calls to say she just found the body. Roger Bower (producer, director), Elaine Kent, Raymond Edward Johnson, William Podmore, Eleanor Phelps, Paul Hammond, Shirling Oliver, Barry Thompson, Helen Riley (author), Stedman Coles (adaptor). oldtimeradiodvd.com

Richard chats with Jeffrey Snover about DevOps at Microsoft. The concept of DevOps goes back to a talk that John Allspaw and Paul Hammond did at Velocity called 10 Deploys Per Day. DevOps focuses on having developers and operations working closely together to make rapid deployments possible. Jeff discusses his blog post on the subject of Windows Server 2012, PowerShell 3.0 and DevOps. DevOps is coming to the Microsoft world, are you ready?

This is Part 3 of a four part interview that Peter Stanway did with presenter Paul Hammond on UCB Radio....each part is approximately five minutes long.

This is Part 2 of a four part interview that Peter Stanway did with presenter Paul Hammond on UCB Radio....each part is approximately five minutes long.

This is Part 1 of a four part interview that Peter Stanway did with presenter Paul Hammond on UCB Radio....each part is approximately five minutes long.

This is Part 4 of a four part interview that Peter Stanway did with presenter Paul Hammond on UCB Radio....each part is approximately five minutes long.

Crime Club was a Mutual Network  murder and mystery series, a product of the Doubleday Crime Book Club imprints found weekly in bookstores everywhere. The telephone rings"Hello, I hope I haven't kept you waiting. Yes, this is the Crime Club. I'm the Librarian. Murder Rents A Room? Yes, we have that Crime Club story for you.Come right over. (The organist in the shadowed corner of the Crime Club library shivers the ivories) The doorbell tones sullenly"And you are here. Good. Take the easy chair by the window. Comfortable? The book is on this shelf." (The organist hits the scary chord) "Let's look at it under the reading lamp." The Librarian, played by Raymond E. Johnson,  begins reading the tale. Veteran Willis Cooper (Lights Out, Quiet Please) did some of the scripts from the Crime Club books.THIS EPISODE:September 11, 1947. Mutual network. "Fish For Entree". Sustaining. A corpse with a dead fish in his pocket is fished out of the harbor. Stedman Coles (writer), Walter Kinsella, Virginia Dwyer, Bill Smith, Julie Stevens, Paul Hammond. 1/2 hour.

Atomic Rooster - Night Living I thought it was high time I started featuring early prog and metal in addition to psych rock. Those genres were born from the experimentation of psychedelia, so it seemed like a logical extension of my psychedelic theme, and it gives me the opportunity to shake things up from time to time. With a name like Atomic Rooster, you might get the idea that this is a psychedelic rock band anyway, sort of like Strawberry Alarm Clock. Make no mistake, this Rooster was crowing to a different tune. Atomic Rooster, formed by Vincent Crane and Carl Palmer in 1969, was one of the premier English heavy metal/prog rock bands. Crane and Palmer had previously been members of The Crazy World Of Arthur Brown, who had a huge hit in 1968 with Fire. That's Crane on the badass Hammond organ part in that song. Palmer didn't stick with Rooster for long, since he went off to drumming fame with Keith Emerson and Greg Lake in their little prog outfit, and was replaced by Paul Hammond. Crane added John Du Cann on guitar, as well, to deepen the band's guitar sound. I found this little gem of a song in a compilation in Mojo Magazine late last year, Heavy Nuggets, which has been lots of fun to explore. This Atomic Rooster cut was pulled from an anthology of lives, rares, and B-sides, Atomic Rooster: The First 10 Explosive Years. If you're not a huge prog fan, worry not. This song leans more toward the heavy metal sound. In fact, it reminds me of Deep Purple or of one of the songs from the Heavy Metal soundtrack, which hubby and I played ad nauseum on the car cassette player back in the day. I love the heavy-handed organ in the song, which, when accompanied by the sinister vocals, give this song that dark metal bent.

Over the last year the Yahoo! Developer Network has opened up dozens of sites and services to external software developers, with APIs for Yahoo! Search, Flickr, del.icio.us, Yahoo! Maps, and many others. More recently Yahoo! has started adopting microformats on Yahoo! Local and Upcoming.org. Simon and Paul peek behind the Yahoo! firewall, showing how these services are created and discussing some of the lessons learned in releasing them to the public. They also show how a company can make use of web services internally to solve real-world technical problems, encourage innovation, and make work more enjoyable.