British Roman client king
POPULARITY
4 episodes with Verica
2 episodes with Verica
2 episodes with Verica
2 episodes with Verica
2 episodes with Verica
3 episodes with Verica
2 episodes with Verica
2 episodes with Verica
In today's episode of Category Visionaries, we speak with Casey Rosenthal, CEO of Verica. Topics Discussed: Chaos engineering - what does it mean? Why is it so important and what impact can it have on an enterprise tech setup Why more and more companies are seeking to add chaos engineering to their approach, and why it's already popular in fintech Why diversity is key for modern tech companies, driving better performance and ultimately more success Continuous verification and the DevOps revolution - where does this new category stand in the story? How harmonizing schedules between different departments can be a real challenge for a company looking to expand Favorite book: What Works: Gender Equality by Design
Välkommen till Apotek Hjärtat! Det här avsnittet vänder sig till dig som snart ska börja på vårt E-apotek. Hör Verica, Klas, Madeleine, Mohammad och Nadia dela med sig av sina upplevelser av att vara ny på Hjärtat, för att ge dig en bättre bild av din nya arbetsplats och hur din första tid hos oss kommer att se ut. Vi ser fram emot att du ska börja hos oss! Hosted on Acast. See acast.com/privacy for more information.
Love is truly in the air on this VERY special episode of The H3 Podcast. Will Jeff truly find love on the sandy shores of Los Angeles with the Australian Verica? Or will he hear the siren's call from offshore of Morgan or Maegan? Tune in to find out on this final episode of The Bach3lor! Learn more about your ad choices. Visit megaphone.fm/adchoices
Nova epizoda nesalomivog podkasta "Dobar loš zao" je stigla u vaše domove! Nenad Kulačin i Marko Vidojković su u prvom delu emisije sa umerenom dozom podsmeha pozdravili Guzonjinu najavu beogradskih izbora za drugi juni, svim srcem podržali inicijativu opozicije i ProGlas-a da se dođe do iole normalnih izbornih uslova, utvrdili da ne moraš da koristiš Skaj da bi se našao u Skaj prepiskama, a zapitali su se i ko to kompromitujućim fotkama pokušava da smesti budućem visokom državnom funkcioneru Marku Đuriću. Gošća je urednica "IN Medija", nezavisnog inđijskog portala i žrtva višegodišnjeg režimskog nasilja, Verica Marinčić. Verica je ispričala do detalja kako je Inđija od simbola demokratije postala simbol naprednjačkog terora, naširoko opisala kako nju, ali i političke neistomišljenke šikanira lokalna vlast, a iznela je i svoje viđenje o predstojećim izborima. U Magarećem kutku čeka vas neuobičajeno skandiranje na stadionu "Rajko Mitić". DLZ, jedini podkast na Balkanu pod zaštitom Međunarodnog PEN centra.
Retired Agent Barbara Verica reviews her espionage assignment working as a first-time, untrained, undercover agent (UCA) in Manhattan, gathering intelligence and the evidence to prove that Norwegian diplomat Arne Treholt was selling secrets to the former Soviet Union. The investigation was initiated on behalf of the Norwegian security service who had received information that Treholt, assigned as a member of the Norwegian delegation to the United Nations, was a spy. Barbara's assignment—move into the apartment next door and track Treholt's movements. But things quickly became much more complex when Barbara became friends with Treholt's wife. Barbara served in the FBI for 30 years. This case review is a do-over of the missing Episode 18, removed from the back catalog a few years ago. Check out episode show notes, photos, and related articles: https://jerriwilliams.com/304-barbara-verica-tracking-arne-treholt-soviet-spy/ Buy me a coffee - https://www.buymeacoffee.com/JerriWilliams Join my Reader Team to get the FBI Reading Resource - Books about the FBI, written by FBI agents, the 20 clichés about the FBI Reality Checklist, and keep up to date on the FBI in books, TV, and movies via my monthly email. Join here. http://eepurl.com/dzCCmL Check out my FBI books, non-fiction and crime fiction, available as audiobooks, ebooks and paperbacks wherever books are sold. https://jerriwilliams.com/books/
The one where *Note: this episode was recorded in June before the WGA and SAG-AFTRA strikes were announced* Emma and Nicole speak to Tom Verica, the director of Queen Charlotte, one of the most popular Netflix shows to date. He is currently the head of creative production for Shondaland and has an extensive career on stage and screen as actor, director and executive producer. We dive into the secrets of the Bridgerton universe's success, "The Great Experiment," the importance of collaboration, and the portrayal of interracial relationships on screen. Preorder our book The Half Of It: https://amzn.to/3rDq1qo Our website: https://www.mixedup.co.uk/ Our Patreon: https://www.patreon.com/mixeduppodcast Our Instagram: https://instagram.com/mixedup.podcast Tom's Instagram: https://www.instagram.com/tomverica
This week Mariel and Melissa welcome Tom Verica, actor, director, and executive producer of the highly acclaimed "Queen Charlotte: A Bridgerton Story." Join us on a mesmerizing behind-the-scenes journey, delving into the meticulous research and exploration conducted to portray King George's mental health in this compelling spin-off. Discover the challenges and complexities involved in authentically capturing a historical figure's emotional well-being within the enchanting world of Bridgerton. Verica reveals how the talented team of "Queen Charlotte: A Bridgerton Story" seamlessly weaves together history, storytelling, and character development to create a captivating viewing experience. Follow Tom on Instagram: @tomverica Follow Tom on Facebook: @thomasverica Follow Tom on Twitter: @tomverica Hosts - Mariel Hemingway & Melissa Yamaguchi Executive Producer - Jeremiah D. Higgins Senior Sound Engineer - Richard Dugan Producer and Sound Engineer - Slater Smith Click to Donate to the Mariel Hemingway Foundation Follow us on Instagram Subscribe to the Mariel Hemingway Foundation Youtube channel here
Today Mariel & Melissa welcome the incredibly prolific TV/Film creator Tom Verica! Tom Verica has an illustrious career as a gifted actor, director and executive producer. Tom Verica is the Head of Creative Production for Shondaland/Netflix. He is Executive Producer and the Director of Queen Charlotte: A Bridgerton Story - Stream it Now on Netflix! Tom was nominated for an Emmy Award for Outstanding Limited Series as an Executive Producer and a Directors Guild Award for Best Director of a Limited Series for INVENTING ANNA. He has been a longtime collaborator with Shonda Rhimes, which includes work as Executive Producer and Director of SCANDAL and FOR THE PEOPLE. Keep Up with Tom on his socials: Instagram: @tomverica Facebook: @thomasverica Twitter: @tomverica https://www.imdb.com/Tom Verica Hosts - Mariel Hemingway & Melissa Yamaguchi Executive Producer - Jeremiah D. Higgins Senior Sound Engineer - Richard Dugan Producer and Sound Engineer - Slater Smith Click to Donate to the Mariel Hemingway Foundation account.venmo.com/u/MHFOUNDATION Follow us on Instagram www.instagram.com/marielhemingwayfoundation/ Subscribe to the Mariel Hemingway Foundation Youtube Channel Here www.youtube.com/channel/UCR168j3R1Mtx0iUQXs-VigA
Tom Verica is the Head of Creative Production for Shondaland/Netflix. He is Executive Producer and the Director of Queen Charlotte: A Bridgerton Story - Stream it Now on Netflix! Did you hear what he said?! Podcast SN1|Ep4 - Tom Verica - OCTS
Courtney Nash and Casey Rosenthal from Verica join Matty for a deep dive into the results of the VOID (Verica Open Incident Database) report.
Courtney Nash and Casey Rosenthal from Verica join Matty for a deep dive into the results of the VOID (Verica Open Incident Database) report.
To mark IWD, Radio Works hosts a double bill of inspiring individuals. Verica Djurdjevic is the Chief Revenue Officer at Channel 4, recruited from the planning-led media agency, PHD. Verica took over during the lockdown of winter 20, and has guided the biggest youth-reach medium through the changes in viewing behaviour, whilst at the same time developing new opportunities offered by evolving platforms. Through her experience and skillset she has given the channel a revived purpose and this is a fascinating insight into the mind of a leader navigating one of the most complex media channels with strategy and execution in perfect harmony. Hosted on Acast. See acast.com/privacy for more information.
In today's episode of Category Visionaries, we speak with Casey Rosenthal, CEO of Verica, about his career in digital security, making a name for himself with the concept of chaos engineering, and how he eventually took those ideas mainstream with Verica, a continuous verification platform which helps people map the limitations of their existing software solutions and make contingencies for when things go wrong. An increasingly popular concept, ‘chaos engineering' is essentially a toolkit to experiment with a system's critical capacity, but a great tool doesn't always make a perfect product, and Carey explains a little bit about how commercial viability can be an engineering challenge all of its own, why continuous verification is the final piece of the DevOps revolution, and why the biggest challenge for Verica is aligning disparate development cycles. Topics Discussed: Chaos engineering - what does it mean? Why is it so important and what impact can it have on an enterprise tech setup Why more and more companies are seeking to add chaos engineering to their approach, and why it's already popular in fintech Why diversity is key for modern tech companies, driving better performance and ultimately more success Continuous verification and the DevOps revolution - where does this new category stand in the story? How harmonizing schedules between different departments can be a real challenge for a company looking to expand Favorite book: What Works: Gender Equality by Design
Tom Verica, director and Head of Creative Production at Shondaland returns as host Gabrielle Collins and Charithra Chandran (Edwina Sharma) unpack the wild ride of Episode 6, “The Choice.” Charithra describes Edwina's character growth as she finds her voice, plus Tom explores behind-the-scenes extras from the set. You can (re)watch Bridgerton on Netflix now! See omnystudio.com/listener for privacy information.
Simone Ashley (Kate Sharma) and Tom Verica, director and Head of Creative Production at Shondaland walk host Gabrielle Collins through the pivotal turning point of the season, Episode 5, “An Unthinkable Fate.” Our guests explore the continuous increase of tension through Kate and Anthony's relationship and the tumultuous dinner scene at the Bridgerton estate. You can (re)watch Bridgerton on Netflix now! See omnystudio.com/listener for privacy information.
Welcome back to the OWASP podcast. In this episode, we're headed to The VOID. I speak with Courtney Nash about the Verica Open Incident Database, otherwise known as The VOID, which is a collection of software-related incident reports available at https://www.thevoid.community/. It's a fascinating discussion about how, by gathering data from The VOID, we can make the Internet a safer and more resilient place. Courtney was super passionate about the research work she's doing. It was completely fun to chat with her and they've already produced some very interesting conclusions, in the published report available on The VOID website. I had a blast recording this one and I hope you enjoy it. EPISODE LINKS - The VOID: https://www.thevoid.community/ - 2021 Report: https://www.thevoid.community/report - Podcast: https://podcast.thevoid.community/ - Google MTTR report: https://www.oreilly.com/library/view/incident-metrics-in/9781098103163/ (Summarized also in the 2021 VOID report)
Hey, want to know an example page where you could find all the scenarios to practice your test automation skills. How do you deploy Jmeter on AWS using TerraForm? And do you know, the adoption of APIs is on the rise? How can you make sure that your security is keeping up with this development? Final answers to these and all other and full pipeline DevOps automation, testing, performance, testing, and security testing in this episode of the Test Guild new show for the week of January 23rd. So give yourself a cup of coffee or tea, and let's do this. 0:29 Applitools Free Account https://rcl.ink/xroZw 1:03 XPath Practice Page https://links.testguild.com/XcbFe 1:42 Applitools win's DevOps Dozen https://links.testguild.com/3NQFy 2:30 Cypress 9.3 https://links.testguild.com/HBiNh 3:00 Testcontainers-java 1.16.3 is out! https://links.testguild.com/xHJ6B 3:47 Migration to the Cloud https://links.testguild.com/csBcC 4:35 Reduce Test Failures in CI/CD Pipelines? https://links.testguild.com/RY6wm 5:08 Verica raises $12M https://links.testguild.com/ZibfC 6:08 Automation Predictions: https://links.testguild.com/jgFkA 6:39 Deploy JMeter on AWS using Terraform https://links.testguild.com/vrUnv 7:20 API Security: https://links.testguild.com/FO6hl 8:22 Cisco Security Issue: https://links.testguild.com/0rz1P
Dave, Mark and Mike discuss their best bits from the DevOps Enterprise Summit 2021 with IT Revolution. They also review their talk on the Serverless Value Flywheel. The DOES 2021 talks are practical with participants describing their digital transformation journeys in an open way, revealing the lessons they have learned. Here are quick links to themes, tools and techniques that the guys covered in their talk on the Value Flywheel and picked up in other talks and discussions: https://learnwardleymapping.com https://doctrine.wardleymaps.com https://medium.com/wardleymaps https://list.wardleymaps.com https://github.com/ddd-crew/ddd-starter-modelling-process… https://amplitude.com/north-star Our Talk: 'The Serverless Edge, Using Wardley Mapping with the Value Flywheel from combined Business and Technology Evolution' Transcript: https://www.theserverlessedge.com/wardley-mapping-with-the-value-flywheel/ Slides: (including ours under Dave Anderson): https://github.com/devopsenterprise/2021-virtual-us Slack: https://devopsenterprise.slack.com/ New Book announcement https://itrevolution.com/announcing-new-book-from-david-anderson/ The conference was virtual but there were still many opportunities to interact through the Slack Channel and Lean Coffees with leaders and architects from leading edge organisations. Dave and Mark also give a behind the scenes view of their talk: The Serverless Edge, Using Wardley Mapping with the value Flywheel from combined Business and Technology Evolution which previewed their book due to publish next year with IT Revolution: https://itrevolution.com/announcing-new-book-from-david-anderson/ In their talk they explained what a 'value flywheel' is and they did a live demo of a Wardley Map to show the technique in action. There are 4 stages of the 'value flywheel': 1. Clarity of Purpose 2. Challenge 3. Next Best Action 4. Long Term Value The transcript for talk is available on: https://www.theserverlessedge.com/wardley-mapping-with-the-value-flywheel/ Dave and Mark hosted a Lean Coffee on 'Building internal capability, not consultancy dependency', which prompted a good debate. Mike also picked up on themes around value streams and flow efficiency with Mik Kersten from Tasktop - tasktop.com, and similarly with Bank of New Zealand - bnz.co.nz. The guys felt that Wardley Mapping is very complimentary to those themes and is rising in popularity. Mark picked up on an increasing evolution towards product centricity, meaningful work and socio technical practice. Mike attended a session looking at ubiquitous language tying in with the need for visibility/observability to make decisions in DevOps organisations which Mark also picked up on in the talk on 'shifting left with product excellence' with Liz Fong-Jones with metrics being used in right way being key. Mike also picked up a lot of SRE themed talks including one by Michael Winslow from Comcast. Courtney Nash from Verica and Troy Koss from Capital One did a 'Chaos and Reliability: A Surprising Friendship in the Enterprise' talk that Mark enjoyed. And Dave picked up on a talk by Dr. Ron Westrum. Mike felt that Team Topologies concepts were permeating the talks and thinking at the conference. Dave enjoyed the talk with Admiral John Richardson and the ultimate distributed organisation, leadership and autonomous themes. Security was covered by John Wallace looking at how that area has changed. The guys picked up on the lack of serverless talks, although that could be about the organisational journey. Also the conference wasn't really about specific technologies. Tune in next time for more conversation on all things Serverless Craic. Serverless Craic from The Serverless Edge theserverlessedge.com @ServerlessEdge
Wir sprechen mit Univ. Prof. Dr. Verica Trstenjak, Universitätsprofessorin und ehemalige Generalanwältin beim EuGH. Wir thematisieren Funktion und Interpretation europäischer Grundrechte in der Krise. Links: https://intersentia.com/en/coronavirus-and-the-law-in-europe.html https://www.pf.um.si/en/about/employees/teachers-and-researchers/full-professors/verica-trstenjak/
Courtney Nash of Verica joins Dennis Fisher to talk about the new Verica Open Incident Database, which centralizes reports of software outages, security incidents, and near misses, and why studying the way systems fail is so valuable.
In this episode, we brought in two exceptional guests that are no stranger to chaos. In fact, they've identified ways to engineer for chaos. In the studio, we have Aaron Rinehart, CTO, and founder at Verica. We also have Jamie Dicken, former manager of applied security at Cardinal Health and current director at Resilience. These two are also authors of Security Chaos Engineering. If you haven't read that book it's already out, you should check it out. Chaos engineering is the technique of introducing turbulent conditions into a distributed system to try to determine the conditions that cause it to fail before it actually fails. So they simplify it. What we do with chaos engineering is learn about the system without experiencing the pain of an outage or an incident. You learn to trust your gear by testing. The biggest impact really came once we understood how security chaos engineering fits into the bigger security picture. It's not about just being a part of the latest and greatest techniques and having the excitement of doing something that's cutting edge, but security chaos engineering at the end of the day. It's useless unless what you've learned drives change. Key Takeaways: 0:00 Previously on the show 1:40 Aaron Rinehart and Jamie Dixon introduction 2:08 Episode begins 2:59 What Jamie and Aaron are doing today 3:13 What Jamie is doing 4:13 What Aaron is doing 5:00 Discuss chaos engineering 9:26 Importance of chaos engineering 10:16 Myths of chaos engineering 12:55 Chaos engineering customer impacts 17:34 Learning to trust the test and end result 19:03 Reader and customer feedback 22:21 Chaos engineering gone wrong 27:39 Implementing change in cybersecurity 28:11 Building a team of experts 39:08 Getting involved in chaos engineering 41:09 Tools for listeners 43:25 Keeping up with Aaron and Jamie Aaron Rinehart on Twitter aaron@verica.io Jamie Dicken on Twitter Verica on LinkedIn Verica Free Book Learn more about Hacker Valley Studio Support Hacker Valley Studio on Patreon Follow Hacker Valley Studio on Twitter Follow Ron Eddings on Twitter Follow Chris Cochran on Twitter Sponsored by Axonius
About CourtneyCourtney Nash is a researcher focused on system safety and failures in complex sociotechnical systems. An erstwhile cognitive neuroscientist, she has always been fascinated by how people learn, and the ways memory influences how they solve problems. Over the past two decades, she's held a variety of editorial, program management, research, and management roles at Holloway, Fastly, O'Reilly Media, Microsoft, and Amazon. She lives in the mountains where she skis, rides bikes, and herds dogs and kids.Links: Verica: https://www.verica.io Twitter: https://twitter.com/courtneynash Email: courtney@verica.io 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: This episode is sponsored in part by our friends at Jellyfish. So, you're sitting in front of your office chair, bleary eyed, parked in front of a powerpoint and—oh my sweet feathery Jesus its the night before the board meeting, because of course it is! As you slot that crappy screenshot of traffic light colored excel tables into your deck, or sift through endless spreadsheets looking for just the right data set, have you ever wondered, why is it that sales and marketing get all this shiny, awesome analytics and inside tools? Whereas, engineering basically gets left with the dregs. Well, the founders of Jellyfish certainly did. That's why they created the Jellyfish Engineering Management Platform, but don't you dare call it JEMP! Designed to make it simple to analyze your engineering organization, Jellyfish ingests signals from your tech stack. Including JIRA, Git, and collaborative tools. Yes, depressing to think of those things as your tech stack but this is 2021. They use that to create a model that accurately reflects just how the breakdown of engineering work aligns with your wider business objectives. In other words, it translates from code into spreadsheet. When you have to explain what you're doing from an engineering perspective to people whose primary IDE is Microsoft Powerpoint, consider Jellyfish. Thats Jellyfish.co and tell them Corey sent you! Watch for the wince, thats my favorite part.Corey: This episode is sponsored in part by our friends at VMware. Let's be honest—the past year has been far from easy. Due to, well, everything. It caused us to rush cloud migrations and digital transformation, which of course means long hours refactoring your apps, surprises on your cloud bill, misconfigurations and headache for everyone trying manage disparate and fractured cloud environments. VMware has an answer for this. With VMware multi-cloud solutions, organizations have the choice, speed, and control to migrate and optimizeapplications seamlessly without recoding, take the fastest path to modern infrastructure, and operate consistently across the data center, the edge, and any cloud. I urge to take a look at vmware.com/go/multicloud. You know my opinions on multi cloud by now, but there's a lot of stuff in here that works on any cloud. But don't take it from me thats: VMware.com/go/multicloud and my thanks to them again for sponsoring my ridiculous nonsense.Corey: Welcome to Screaming in the Cloud. I'm Corey Quinn. Periodically, websites like to fall into the sea and explode. And it's sort of a thing that we've accepted happens. Well, most of us have. My guest today is Courtney Nash, Internet Incident Librarian at Verica. Courtney, thank you for joining me.Courtney: Hi, Corey. Thanks so much for having me.Corey: So, I'm going to assume that my intro is somewhat accurate, that we've sort of accepted that sites will crash into the sea, the internet will break, and then everyone tears their hair out and complains on Twitter, assuming that's not the thing that fell over this time—Courtney: [laugh].Corey: —but what does an Internet Incident Librarian do?Courtney: Yeah, I'll come back to the first part about how—some people have accepted it and some people haven't, I think is the interesting part. So technically, I think my official real title is, like, research analyst or something really boring, but I have a background in the cognitive sciences and also in technology, and I'm really—have always been fascinated by how these socio-technical systems work. And so as an Internet Incident Librarian, I am doing a number of things to try to better understand—both for myself and, obviously, the company I work for, but for the industry as a whole—what do we really know about how incidents happen, why they happen, when they happen, and what do we do when they happen? And how do we learn from that? So, one of the first things that I'm doing along those lines is actually collecting a database of all of the public write-ups of incidents that happened at companies that are software-related.So, there's already bodies of work of people who collect airline incidents and other kinds of things. And we don't have that [laugh] as an industry, which I think is—I want to solve that problem because I think other industries that have spent some time introspecting about why things fall down, or when things fall down and how they fall down. Take the airline industry for example; planes don't really fall out of the sky very often.Corey: No. When it does, it makes news and everyone's scared about flying, but at the same time, it's yeah, do you have any idea how many people die in car crashes in a given hour?Courtney: Yeah, yeah. And we'll come back to how the media covers things in a minute because that is definitely something I have opinions about. But, I'm not trying to say I want to create the NTSB of the internet; I don't think that's quite the same thing, and I really want something in the spirit of software, and the internet, and open-source that's more collaborative and it's very open to all of us. So, the first step is to just get them in one place. There is no single place where you could go and say, “Oh, where all of the X incident reports? Where all the ones that Microsoft's written, and also Amazon, or Google, or, you know, whoever.”Corey: They have them, but they hide them so thoroughly. It turns out that they don't really put that in big letters on their corporate blog with links to it. And when you look at one incident report, they don't say, “Here, look at our previous incident reports.” They really—Courtney: Yeah.Corey: —should but no one does.Courtney: And I think that's fascinating because there's a precedent. So, there's two precedents, and I just gave you basically one side of the two, which is, the airline industry has done this and it's not like people don't fly, right? So, a lot of internet companies, a lot of software-based companies, seem to be afraid of what their customers, or what the stock market, or what folks will think. Mind you, these are publicly traded [laugh] airline companies. People aren't going to stop using Amazon just because you give more of this information out.And so I think that piece is—I would love to see that stop being the case. Because the flip side of the coin is that this is a rising tide lifts all boats kind of thing, which granted, not all companies agree on, especially really big ones because their boats already mowing all the little ones out of the ocean. But that's another story.Corey: Sure, but also, it's easy to hide an outage. “Our site is down for you can say three days. Great, if a customer didn't try to access the site at all during those three days, was the site really down in the first place?”Courtney: Oh, the tree in the forest of internet outages. Yes, it's true, although I think that companies are—they know that people go complain on social media, right? I think there's more and more of that happening now. It's not like you can hide it as easily as you could have before Twitter or Instagram or—Corey: Right. Whereas a plane falls out of the sky, generally it's one of those things that people notice.Courtney: Yeah. Even if you weren't interested in that flight at all.Corey: Right. When it lands in your garden, you sort of have a comment on this.Courtney: [laugh]. Yeah. Pieces fall out of the sky. That has happened. But I think the other flip side of the coin I already mentioned is the safety of airline industry has increased so significantly over the past, you know, whatever, 30, 40 years because of this concerted effort.And the other piece of it, then, as an industry, as technologists, as people who use software to run their businesses, some of those things are now safety-critical. And this comes back to the whole software is running the world now. Planes now actually could fall out of the sky because of software, not just because of hardware failures. And nuclear power plants are [laugh] run by software, and your electronic grid, and your health care systems, heart rate monitors, insulin pumps. There are a lot of really critical things, and now our phone services and our internet stuff is so entwined in our lives, that people can't be on their Zoom calls, people can't run their businesses. So, this stuff has a massive impact on people's lives. It's no longer just pictures of cats on the internet, which admittedly, we've really honed the machine for that.Corey: No, but now when software goes down, the biggest arguments people make, the stories people tell is, “Oh, well, it meant that the company lost this much money during that timeframe.” And great, maybe. We can argue about is that really true or is it not? It depends entirely on the company's business model, but I don't like to tend to accept those things at face value. But yeah, that's the small-scale thing, especially when you start getting to these massive platform providers. There are a lot of second and third-order effects that are a lot more interesting slash important to people's lives, than, well, we couldn't show ads to people for an hour and a half.Courtney: Right. Yes. Absolutely. So, T-Mobile had this outage, what is it, how is time—time is still not working very well, for me. I'm trying to remember if it was earlier this year, or if it was in—it was last year. I think it was 2020. And you're like, T-Mobile, oh okay, whatever. You know, like, cell phones, yadda, yadda. 911 stopped working. [laugh].And it was a fascinating outage because these are now actually regulated industries that are heavily software-backed. There was a government investigation into that the same way we have NTSB investigations into airline accidents, and they looked at all of those, kind of, second or third-order effects of people who—you know, a grandma who was stranded on the road, people who couldn't call 911, those kinds of things that are really significant impacts on people's lives. And the second-order effect is, oh, yeah, AWS goes down—like you said—and Amazon or people like to say, Jeff Bezos—I guess, now, are they going to complain about how much money Andy loses? I guess so—but [laugh] what lives on AWS, that's crazy to think about, right?Corey: Yeah, the more I learn the answer to that question, the more disturbed I become.Courtney: Well, you'd probably know a better answer to that question [laugh] than a lot of people.Corey: They have the big companies they can talk about. What's really interesting is the companies that they don't and can't. An easy example: financial services is an industry that is notorious for never granting logo rights. Like, at some point, they'll begrudgingly admit, “Yes, our multinational bank does use computers.” But it's always like pulling teeth, and I get it on some level; the entire philosophy of a lot of these companies is risk-mitigation, rather than growth and advancing the current awareness of knowledge. But it does become a problem.Courtney: Yeah. It's interesting, I need more data, which we'll get to—help me, people—but I am able to start seeing some of those interesting graphs of, kind of these cascading effects of these kinds of outages. And so I strongly believe that we need to talk about them more, that more companies need to write them up, and publish them, and be a lot more transparent about it. And I think there's a number of companies that are showing the way there that—and it has to do with your first question which is, we've all sort of accepted this, right? But I disagree with that.I think those of us who are super close to these kinds of complex, dynamic distributed systems totally know that they're going to fail, and that's not shocking, nor the case of incompetence. We are building systems that are so big and so complex, no one person, no 10X engineer out there could possibly model or hold the whole thing in their head. Especially because it's not even just your systems… we were just talking about, right? Your stuff's on GitHub; it's on AWS; there's, like, three other upstream providers; there's this API from over there. These systems are too intricate, too complex; they're going to fail.Corey: So, we're back to why all these things failed simultaneously and it comes out it's a Northern woods, middle of nowhere backhoe incident. That's right, if we look at the natural food chain of things, fiber optic cable has a natural predator in the form of a backhoe. To the point where if I'm ever lost in the woods, I will drop a length of fiber, kick some dirt over it, wait a few minutes; a backhoe will be along to sever it. Then I can follow the backhoe back to civilization. They don't teach that one and the boy scout manual, but they really should.Courtney: Yeah. Oh, my gosh. There was a beaver outage in Canada, which is the—[laugh] God, that's the most Canadian thing ever.Corey: Can you come up with a more Canadian—Courtney: No.Corey: —story than that? I would posit you could not, but give it a shot.Courtney: No, probably not. Anyhoo. So, I think, like I was saying, those of us close to it accept that, understand it, and are trying to now think about, okay, well, how do we change our approach and our philosophy about this, knowing that things will fall down? But I think if you look at a lot of the rest of the world, people are still like, “What are those idiots doing over there? Why did their site fall down?”Corey: Oh, my God—Courtney: Right?Corey: —the general population is the worst on stuff like this. The absolute worst.Courtney: The media is the worst. [laugh].Corey: It's, “How did they wind up to going down?” “Yeah, because this stuff is complicated.” Back when I was getting started in tech, I thought the whole thing worked on magic, so I started figuring out different pieces of it worked. And now I'm convinced; it runs on magic. The most amazing thing is this all works together. Because—Courtney: Yeah.Corey: —spit and duct tape and baling wire holding this stuff together would be an upgrade from a lot of the stuff that currently exists in the real world. And it's amazing.Courtney: I know the secret, Corey. You know what holds it all together?Corey: Hit me with it. Hope? Tears?Courtney: People.Corey: Mmm.Courtney: Technology is Soylent Green, Corey. It's Soylent Green. It's made of people.Corey: And that's the thing that always bugs me on Twitter. The whole HugOps movement has it right. When you see a big provider taking an outage, all their competitors are immediately there with, “Man, hope things get back together soon. Best of luck. Let us know if we can help.” And that's super reassuring because today is their outage; tomorrow it's yours.Courtney: Yep.Corey: And once in a blue moon, you see someone who's relatively new to the industry starting trying to market their stuff based on someone else's outage, and they basically get their butts fed to them, just because it's this—it's not what you do, and it's not how we operate. And it's one of the few moments where I look at this and realize that maybe people's inherent nature isn't all terrible.Courtney: [laugh]. Oh. Oh, I would hope that would be something that comes out of all of this.Corey: Yeah.Courtney: No one goes to work at their day job doing what we do, to suck. [laugh]. Right? To do a bad job.Corey: Right. Unless you're in Facebook's ethics department, I completely agree with you.Courtney: Okay. Yes. All right. There are a few caveats to that, probably. But you know, we all want to show up and do good stuff. So, nobody's going in trying to take the site down, barring bad actor stuff that's not relevant.Corey: When Azure takes an outage, AWS is not sitting there going, “Ah, we're going to win more cloud deals because of this,” because they're smarter than that. It's, no, people are going to look at this and say, “Ah, see. Told you the cloud was dangerous.” It sets the entire industry back.Courtney: Yeah. That's why we need to talk about it more, and we need to just normalize that these things happen and that we can all level up as an industry if we get a lot smarter about how we, A) think about that, and B) how we react to them. And we will develop much more useful models of our safety boundaries, right? That's really it. You don't know—no one at any of these companies hardly knows if you're five steps from the cliff, five feet, driving a Ferrari 90 miles an hour towards the edge of it.Like, we don't know, it's amazing to me just how much in the dark we are as an industry and how much of the world we're running. So, I think this is one tiny, first little step in what could be sort of a sea change about how all of this works. So, that's a big part of why I'm doing what I'm doing.Corey: Well, let's talk about something else you're doing. So, tell me a little bit about VOID?Courtney: Yeah. So, that's the first iteration of this. So, it's the [Verica Open Incident Database 00:14:10]. I feel like I have to say this almost every time John Allspaw would like me to say that it's the Verica Open Incident Report Database, but VOID is way cooler than—Corey: VOIRD?Courtney: VOIRD.Corey: Yeah, that sounds like you're trying to make fun of someone ineffectively.Courtney: Yeah. And there's a reason why he's not in marketing. But what this is is a collection of all of the publicly available incident reports in one place, easily searchable. You can search by company, you can search by technology, you can filter things by the types of, sort of, kinds of failure modes that we're seeing. And it's, I hope, valuable to a wide swath of folks, both technologists and otherwise: researchers, media and press types, analysts, and whatnot.And my biggest desire is that people will look at it, realize how incomplete it is, and then help me fill it. [laugh]. Help me fill the VOID, people. I think I have right now, at the time we're talking, about 1700, maybe 1800 of these. And they run the gamut. And I know some people who like to quibble about language—and I am one of those people having been an editor in various flavors of my life—not all of these are what a lot of people directly related to these, sort of, incident management and whatnot would call ‘incident reports.'I wanted to collect a corpus that reflects all of the public information about software-related incidents. So, it's anything from tweets—either from a company or just from people—to a status page, to a media article, a news article, an online article, to a full-blown deep-dive retrospective or post-mortem from a company that really does go into detail. It's the whole gamut. It's all of those things. I have no opinionated take on that.I want that all to be available to people. And we've collected some metadata on all of the incidents as well. So, we're collecting the obvious things like when did it happen? What date was it, if we can figure it out, or if it's explicit—how long was it? And those kinds of things and then we collect some metadata, like I said. We add some tags: was this a complete production outage, was it a partial outage? Those kinds of things.And this is all directly just taken from the language of the report. And we're not trying—like I said—we're trying not to have any sort of really subjective takes on any of that, but a bit of metadata that helps people spelunk some of this stuff. So, if it is the kind of report—these are usually from a status page, or a company post about it—what kinds of things were involved in this outage? So, sometimes you'll get lucky and the company will tell you, “It was DNS,” because, you know, it's always DNS.Corey: On some level, it always is. That's why—Courtney: It always is.Corey: —DNS is my database. It's a database problem.Courtney: It's a database problem. And sometimes you get even more detail. And so we will put as much of that that's in the report into a set of metadata about these things. So, I think there's some fascinating, really easy things that I've already seen from some of these data, and we kind of hit on one of these, which is the way that companies themselves talk about these outages versus the way that press and media and other types of organizations talk about these things. So, I think there's a whole bunch of really fascinating analysis that's going to be available to nerdy research-minded type folks like myself.I think it's a place, though, where technologists can also go and spelunk things that they're interested in, looking for patterns, anything that's really—there's an opportunity for experts in the field to add insights to what we can discern from these public incident reports. They are, like, two orders abstracted from what happened internally, but I think there's still a lot that we can learn from those. So, the first iteration of the VOID will allow people to get a first look at some of the data and to help me, hopefully, add to it, grow that corpus over time, and we'll see where that goes.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: I love the idea of having a centralized place where outages, post-mortems, root cause analyses—I'll let you tear into that in a minute—and other things that are all tied to where can I find a list of outages. Because companies list these on their websites, they put them in blog posts, and it's always very begrudging; they don't link them from any other place, you have to know the magic incantation to find the buried link on their site. Having something that is easily searchable for outages is really something that's kind of valuable.Courtney: Yeah. And I mean, some of them are like—I'm looking at you, Microsoft—I like you for a lot of reasons, but hey, I have to scroll your status page. I can't link directly to their write-ups, and—this is Azure—and it [laugh] please stop. Make it easier. [laugh]. You're driving me crazy; I don't even have a data model to figure out how to make this work for people, other than, like, taking screenshots of them.So yeah, so there's shades of grey and black in how much they'll share, or how easy it is to find these things. So, it'll be interesting to see if there's any less-than-positive [laugh] reactions to all of this being available in one place. I'm anticipating at least a little bit of that.There is one other type of metadata that we collect for the VOID. And that is the type of analysis that is conducted if it is clear what that type of analysis is. And there, some companies explicitly say, or call it an RCA, “We did a Root Cause Analysis.” There's a few other types; some people talk about having a Contributing Factors Analysis. Most people don't consider a formal analysis type, but I am trying to collect and categorize these because I do think there are some fascinating implications buried therein, and I would like to see if I can keep track of whether or not those change over time. And yes, you've hit on one of my favorite hot-take soapbox things, which is root cause.Corey: Please, take it away.Courtney: Yeah. Well, and anyone who's close to these systems and has watched these things fall down has the inherent sense that there is no root cause. Like—[laugh]—let's—great. One of my favorite ones: human error. We don't have enough hours for this, Corey. I'm sorry. That's one of my favorite other ones. But let's say somebody fat-fingers a config change. Which happens—Corey: That was fundamentally the S3 service disruption back in—Courtney: Yes.Corey: —2017 that took down S3 for hours on end.Courtney: And took down so many other people that relied on S3.Corey: Everything was tied to that. And that's an interesting question; when something like that hits, does that mean that everything it takes down get its own entry in VOID?Courtney: I hope so. If everybody writes them up, then yes. [laugh]. So, if S3 goes down, and you go down, and you write it up, and you put it in the VOID, then we can see those things, which would be so cool. But let's go back to the fat-fingered config file—which if you haven't ever done, you're lying, first of all—Corey: Or you haven't been allowed to touch anything large and breakable yet, which, either way, you're lying on some level. So, please—Courtney: Yeah. I mean, I took down [Halloway's 00:20:53] homepage when it was on Hacker News because of YAML. So, anywho. Even if you fat-finger a config change, that's not the root cause because you have this system wherein a fat-fingered configure change can take down S3. That is a very big, complex, and I might add, socio-technical system.There are decisions that were made long ago about why it was structured that way, or why this happens that way, or what kinds of checks and balances you have. It's just, get over it people. There is no root cause. These are complex, highly dynamic systems that when they fail, they fail in unpredictable and weird ways because we've built them that way. They're complex because you're successful at pushing the envelope and your safety boundaries.So, if we could get past the root cause thing as an industry, I mean, I could probably just retire happy, honestly. [laugh]. I'm a simple woman; could we just get one thing, people? [laugh]. First of all, then it gives non-technologists, people outside of our bubble, the media, you can't hang it on these things anymore. We all have to then grapple with the complexity, which admittedly humans, not big fans of, but—Corey: People want simple stories, simple narratives. When people say, “Oh, remember the S3 outage?” They don't want to sit there and have to recount 50,000 different details. They want to say, “Oh, yeah. It took down a few big sites like Instagram, United Airlines, and it was a real mess.” The end. They want something that fits in a tweet, not something that fits in a thesis.Courtney: Well, and if you have a single root cause, then you can fix the root cause and it will never happen again. Right?Corey: That's the theory. If we're just a little bit more careful, we're never going to have outages anymore.Courtney: Yeah, if we could just train those humans to not try to make the best possible high-quality decision they could possibly make in that situation given the information they have at the time, then we'll do better. But I mean, that's why your system stay up most of the time, if you think about it. It's shocking how well these things actually work the vast majority of the time. And that's what we could learn from this, too. We could, you know—oh if we would write near-misses up, please.I mean, if I could have one more wish, I think one of the coolest things the airline industry and the government side of that did was start writing up near-misses. It's, wow, what do we learn from when we're successful, versus trying to, like, spelunk and nitpick the failures.Corey: Most of us aren't so good at the whole introspection part. We need failures, we need painful outages to really force us to make difficult, introspective, soul-searching decisions and learn from them.Courtney: Yeah. And I don't disagree with that. I just wish one of the things we would learn is that we should study our successes, too. There's more to be mined from our successes, if we can figure out how to do that, then there is from our failures. So, I have a metadata category in the VOID called ‘near-miss.'And oh man, I really wish people would write those up more. I mean, I think there's, like, five things in there that I've found so far. Because the humans hold these systems together. We make these things work the vast majority of the time. That's why there is no root cause, and even when we're involved in these things, we're also involved in preventing them, or solving them, or remediating them. So, yeah, there's no root cause. Humans aren't the problem. Those are my big hot button ones.Corey: I really wish more places would embrace that. Even Amazon uses the ‘root cause' terminology internally, and I'm not going to sit here and tell them how to run large things at scale; that's what I pay them to figure out for me. But I can't shake the feeling that by using that somewhat reductive terminology that they're glossing over an awful lot of things the rest of us could really benefit from.Courtney: Well, so the question then—one of the other things that I look at is, personally when I read and analyze these incident reports, these public ones a lot, I always ask myself, “Who's the audience for this?” And there are different audiences for different types of incident reports and different things. The vast majority of them are for customers, partners, investors.Corey: The stock market. Yes. Yes.Courtney: They're not actually for the organization. There's usually an internal one that we don't get to see—maybe—that's for the organization. But a lot of places feel that if you have a process, and a template, and a checklist, and a list of action items at the end, then you've done the right thing. You've had your incident, you've talked about it, you've got your action items. Move on.Corey: Right, and it always seems with companies, that as you get further into the company, the more honest and transparent the actual analysis is. Like, at some point, you wind up with the, like, they're very public and very cagey, and under NDA, they open up a little bit more, and a little bit more, and finally, when you work there, their executive team, it turns out, the actual thing was, “Well, Dewey was carrying arm full of boxes in the data center, tripped, went cascading face-first into the EPO cutoff switch that cut power to the entire facility.” The cagier they get, the—I guess, not to be unkind here—but the more ridiculous whatever the actual answer is. It's one of those things where, “Really? Someone tripped and hit a button. You didn't have a plan for that?” “Well, not really. We sort of assumed that people would”—Courtney: Why would you have a plan for that, right?Corey: Right.Courtney: I mean like—[laugh].Corey: Why would you have a plan for that, the first time?Courtney: Yeah. I mean, so imagine this exercise: sitting down in a room with a bunch of people and going, “What are all the things that could go wrong?” I mean, [laugh] ain't nobody got time for that? That's not how it works. You all have other jobs to do, too, and systems to build, and pressures, and customers, and partners, and features to build, so admit and acknowledge that you just won't know all of the antecedents and how do you respond when things happen?Which is a whole other, you know—I know you told me you recorded an episode with Dr. Christina Maslach on burnout, which I'm so happy you did, and there's a whole ‘nother piece of incidents and incident response, and burning people out, and blaming people, and all that stuff that's a whole ‘nother pod—it sounds like you might—you know, probably not incidents with her. But still, these things take a toll on people. And people who, like I said, show up every day really hoping to do their best job, and go up a ladder, and get a promotion, and whatever. So, I think not just treating those things as checklists has broader implications as well, just for the wellbeing of your organization.Corey: On some level, the biggest problem that I think we've run into is that, as you said, it all comes down to people. Unfortunately, legally, we can't patch those. Yet.Courtney: No, [laugh]. No, no. Not most kinds of patches, no. And that's messy. And I know some people are like, “Everyone should learn to code.” And I'm like, “Actually, everyone should get a liberal arts degree.” Come on, help me out people. Because there's so much of these socio-technical systems where the socio part of it is more relevant than the actual technical part.Corey: I believe you're right, for better or worse; there's no way around it. Thank you so much for taking the time to speak with me. If people want to learn more about what you're up to, where can they find you? And we will, of course, throw a link to VOID in the [show notes 00:28:06].Courtney: Yeah, I also like to talk on Twitter, like you do. I'm not as good at it as you are, but I try. So yeah, I'm @courtneynash on Twitter. And at Verica, you can find me at Verica as well, courtney@verica.io. And those are the best ways to find me, I would say. And yeah, please people, write up your incidents, send them to the VOID and let's all learn and get better together, please.Corey: Thank you so much for taking the time to speak with me today. I really do appreciate it.Courtney: Thank you for having me on. I know—do people say this: I'm like, “Yeah, big fan,” but I am. I'm a [laugh] big fan [laugh] of the podcast.Corey: Oh, dear Lord, find better things to listen to. My God.Courtney: [laugh]. But it's been a treat. Thank you.Corey: Courtney Nash, Internet Incident Librarian at Verica. 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've hated this podcast, please leave a five-star review on your podcast platform of choice along with a comment making it very clear that for whatever reason the website is down, it is most certainly not your fault.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.
This interview was recorded for the GOTO Book Club.http://gotopia.tech/bookclubNora Jones - Co-Author of "Chaos Engineering"Casey Rosenthal - Co-Author of "Chaos Engineering"James Wickett - Founder of Open Source Project GauntltDESCRIPTIONToday we have the authors of the Chaos Engineering book sharing key takeaways from the book and from their experience working on chaos projects. This Book Club episode is an expansion of a recent interview between Nora Jones and Casey Rosenthal on the comedic Chaos Community Broadcast [https://chaos.community]. We now include expanded conversation, including discussion about Nora's work with the Learning from Incidents community.Chaos engineering is much more than just hype. Get the map and compass that you need to navigate the stormy waters of distributed systems while optimizing to meet business goals. Casey Rosenthal and Nora Jones, authors of “Chaos Engineering,” highlight some of the best practices that famous companies like Netflix and Capital One use to break (or not break) their systems in productions, so that you can get a taste of it.The interview is based on Nora Jones's and Casey Rosenthal's new book "Chaos Engineering": https://www.verica.io/bookRead the full transcription of the interview here:https://gotopia.tech/bookclub/episodes/getting-started-with-chaos-engineeringRECOMMENDED BOOKSAaron Rinehart • Security Chaos Engineering • https://www.verica.io/sce-bookNora Jones & Casey Rosenthal • Chaos Engineering • https://www.verica.io/bookNora Jones & Casey Rosenthal • Chaos Engineering • https://amzn.to/3hUmuAHMikolaj Pawlikowski • Chaos Engineering • https://amzn.to/2SQ5OlfRuss Miles • Learning Chaos Engineering • https://amzn.to/3hCiUe8Murphy, Beyer, Jones & Petoff • Site Reliability Engineering • https://amzn.to/2Vg6Mbrhttps://twitter.com/GOTOconhttps://www.linkedin.com/company/goto-https://www.facebook.com/GOTOConferencesLooking for a unique learning experience?Attend the next GOTO conference near you! Get your ticket at http://gotopia.techSUBSCRIBE TO OUR YOUTUBE CHANNEL - new videos posted almost daily.https://www.youtube.com/user/GotoConferences/?sub_confirmation=1
On today's conversation, Kaily chats with Shondaland's Senior Creative Production Advisor, Tom Verica. Tom discusses his unconventional path to directing television, as well as his desires and strategies for championing new directors into the industry.At Shondaland, Tom aids in the creative vision and production for all series' or films produced and acts as a liaison for talent and new showrunners. As an actor, you'll recognize Tom from his work playing Jack Pryor in the NBC drama "American Dreams" and Viola Davis' husband Sam Keating on ABC's "How to Get Away with Murder;" among others. As a director he's helmed over 100 episodes for numerous television shows including the popular Shondaland series, “Bridgerton”—the most watched series debut in Netflix history—on which Tom also served as a consulting producer. He is currently overseeing and co-executive producing the second season of the series, as well as the upcoming highly anticipated series “Inventing Anna.”
Casey Rosenthal is the co-founder and CEO of Verica and the former Engineering Manager of the Chaos Engineering team at Netflix. He is an author and thought leader in chaos engineering, “a discipline of experimenting with software systems in production in order to build confidence in the system's capability to withstand unexpected and turbulent conditions.” Casey was an early engineer and champion of chaos engineering, bringing together people from companies like Netflix, Google, Facebook, and Amazon to explore the field. In this week's Unlearned Podcast, Casey and Barry O'Reilly talk about the chaos engineering domain and how to apply its principles to build high-performance teams and businesses. Origins of Chaos Engineering Netflix's migration to the cloud, in particular the sudden outages and service disruptions that would occur, spurred the creation of a program they called Chaos Monkey. “So Chaos Monkey would for each service inside Netflix, every day it would randomly choose an instance and turn it off,” Casey tells Barry. The underlying principle was that once engineers knew a problem existed, they would fix it. “It changed their behavior by aligning the organization around the business problem that needed to be solved,” he remarks. He shares the early Chaos Community Days, bringing colleagues together from leading tech companies to build the discipline they would call chaos engineering. Navigating Complexity Chaos engineering assumes that you already have complexity in your system. “This is engineering to navigate it, or to surface it so that you're aware of it,” Casey explains. Once you're aware a problem exists, you can take steps to fix it. It's a proactive approach to improving availability and security, which improves your system overall. He shares an example of how United Health Group was able to discover a system vulnerability they didn't know they had, and allocate appropriate resources to strengthen their position. Barry comments, “The thing that's very contrary with this is that it's not about people trying to predict the future, it's about them having the data to understand how the systems are performing and then taking action based on that.” Relearning Leadership “Unlearning management is relearning leadership”, Barry says. He asks Casey to share lessons he learned that he is bringing to his new company. Managers are creatures of habit, and that holds them back, Casey responds. “Most of us think we're making decisions when we're not; we're just following habit.” He tries to formulate his own management principles and strategies in his company, instead of following traditional ideas. He believes a manager's job is to ensure their team has the context they need to make the right decisions. His litmus test is this: if your employees can explain why what they're working on is the most important thing they could be working on for the company right now, then you are a successful manager. Read the full show notes at BarryOReilly.com Resources Casey Rosenthal on LinkedIn | Twitter Verica.io
Leah Cunningham is a technology professional with over twenty years of experience building, leading, and coaching teams to maximize value, delivery, and quality. She joins Ryan Shriver for EP 21. They cover chaos engineering, the benefits of task conflict, best practices for managing teams, acknowledging fallibility in leadership roles, the importance of playing > planning, and so much more. Connect with Leah: LinkedIn Verica Chaos Engineering Casey Rosenthal Accelerate, Nicole Forsgren Ph.D., Jez Humble, and Gene Kim Mob Programming, Woody Zuill Semantic Diffusion, Martin Fowler Revenge of the PMO, Marty Cagan Spaghetti Tower Marshmallow Challenge The Electric Fetus, Minneapolis MN Leah's soundtrack: Grant Green, Miles Davis, John Coltrane, Trampled by Turtles
In this episode, we brought in two exceptional guests that are no stranger to chaos. In fact, they've identified ways to engineer for chaos. In the studio, we have Aaron Rinehart, CTO, and founder at Verica. We also have Jamie Dicken, former manager of applied security at Cardinal Health and current director at Resilience. These two are also authors of Security Chaos Engineering. If you haven't read that book it's already out, you should check it out. Chaos engineering is the technique of introducing turbulent conditions into a distributed system to try to determine the conditions that cause it to fail before it actually fails. So they simplify it. What we do with chaos engineering is learn about the system without experiencing the pain of an outage or an incident. You learn to trust your gear by testing. The biggest impact really came once we understood how security chaos engineering fits into the bigger security picture. It's not about just being a part of the latest and greatest techniques and having the excitement of doing something that's cutting edge, but security chaos engineering at the end of the day. It's useless unless what you've learned drives change. Key Takeaways: 0:00 Previously on the show 1:40 Aaron Rinehart and Jamie Dixon introduction 2:08 Episode begins 2:59 What Jamie and Aaron are doing today 3:13 What Jamie is doing 4:13 What Aaron is doing 5:00 Discuss chaos engineering 9:26 Importance of chaos engineering 10:16 Myths of chaos engineering 12:55 Chaos engineering customer impacts 17:34 Learning to trust the test and end result 19:03 Reader and customer feedback 22:21 Chaos engineering gone wrong 27:39 Implementing change in cybersecurity 28:11 Building a team of experts 39:08 Getting involved in chaos engineering 41:09 Tools for listeners 43:25 Keeping up with Aaron and Jamie Aaron Rinehart on Twitter aaron@verica.io Jamie Dicken on Twitter Verica on LinkedIn Verica Free Book Learn more about Hacker Valley Studio Support Hacker Valley Studio on Patreon Follow Hacker Valley Studio on Twitter Follow Ron Eddings on Twitter Follow Chris Cochran on Twitter Sponsored by Axonius
Aaron Rinehart is expanding the possibilities of chaos engineering to cybersecurity. He began pioneering security in chaos engineering when he released ChaoSlingr during his tenure as Chief Security Architect at UnitedHealth Group (UHG). Rinehart is the O'Reilly Author on Security Chaos Engineering and has recently founded a chaos engineering startup called Verica with Casey Rosenthal from Netflix. Aaron joins us to explain what the heck security chaos engineering is. We explore the origin story of chaos engineering and security chaos engineering and how a listener starts with this new technique. We hope you enjoy this conversation with...Aaron Rinehart.
Hello my Love, in der heutigen Podcast-Folge lernst Du Verica Pavlovic (im Folgenden Veri) kennen. Veri ist die Founderin von Brautatelier Tara in Stuttgart und berichtet in dieser Podcast-Folge über ihren Weg und die Liebe zu sich selbst. Sie ist eine sehr inspirierende Persönlichkeit, die ihr eigenes Business aufgebaut und mit Hilfe von Coaching zu sich selbst gefunden hat. Warum Intuition in ihrem Leben eine besondere Rolle spielt, teilt sie mit Dir in dieser Podcast-Folge. Veri findest du auf Instagram unter @veri_verica Ihr Brautatelier findest Du hier: @brautatelier_tara oder über die Website Ihre eigene Schmuckkollektion findet ihr hier: www.juvelan.net/produkt-kategorie/veri-x-juvelan Wir sind sehr dankbar für die tollen Einblicke in das Leben von Veri und wünschen Dir ganz viel Spaß beim Zuhören. Follow us on Instagram @tiffany.licker oder @learntoloveyourself.de Dein LLY-Team
Software Engineering Radio - The Podcast for Professional Software Developers
Aaron Rinehard, CTO of Verica and author, discusses security chaos engineering (SCE) and how it can be used to enhance the security of modern application architectures.
Jason is joined by Paul Verica to discuss getting out of Italy during Covid, the Stanley, and his new restaurant Orto.
Ernest has a degree in electrical engineering from Rice University has been working in technology and technology management for more than 25 years, ranging from enterprises like FedEx, National Instruments, and AT&T cybersecurity to startups like Bazaarvoice, CopperEgg, Precision Autonomy, and Verica. He's been a web developer, operations engineer, product manager, engineering director, and more. He advocates for using Agile, Lean, DevOps, and smart management processes to solve business problems in a fast-moving world. Ernest is noted leader in the DevOps movement and the Austin technical community. He helps organize the CloudAustin user group and the DevOpsDays Austin and All Day DevOps conferences. He blogs with a cadre of like-thinking professionals at theagileadmin.com. Currently, Ernest resides in Round Rock, Texas. His engineering team at Verica develops a product that performs chaos engineering experiments for Kubernetes, to help enterprises use continuous verification to ensure the resilience of their systems.
This week, Content Marketing Manager and host Rin Oliver was joined by Karthik Gaekwad, who is Head of Cloud Native Engineering at Verica and a devopsdays organizer. This podcast episode explores Karthik's journey to extreme testing, continuous verification, QA best practices, and some stellar resources.
Bližamo se stoti obletnici koroškega plebiscita (10. oktober). V oddaji smo predvajali odlomke predavanja zgodovinarja Štefana Pinterja, ki ga je imel na letošnjem Novoletnem srečanju v Tinjah in kjer je predstavil propagandno gradivo iz časa plebiscita, ki ilustrira, iz katerih motivov so se ljudje tedaj odločali za Jugoslavijo ali za Avstrijo. V oddaji tudi novica o tem, da je dr. Edi Gobec iz Clevelanda prejel red za zasluge RS, obisku ministrice Jaklitsch pri škofu Štumpfu in odprtju prehoda Verica - Čepinci.
In this episode of the Virtual Coffee with Ashish edition, we spoke with Aaron Rinehart, CTO Co-Founder Verica. This is episode not to miss. Host: Ashish Rajan - Twitter @hashishrajan Guest: Aaron Rinehart - Linkedin Aaron & Ashish spoke about Who is A-aran? :) What was your path into CyberSecurity or your current role? What is Chaos Engineering? Is Fuzzing part of Chaos Engineering? Is Chaos Engineering for SREs? Is there an example of application fault injection from a cloud perspective? What concepts of Chaos Engineering are people not talking about? Does Chaos Engineering need to happen in production? How does Chaos Engineering affects readiness in terms of incident response? Would Chaos Engineering be part of a Table Top Exercise with executives? How does Chaos Engineering affect automation and Security? What are the trends that you are seeing in Chaos Engineering? Is Cloud Transformation the right time to trigger Chaos Experiments? Is there a Maturity Model to Chaos or Chaos is offered as a service? What are the elements to building a business case for chaos engineering to get support from business stakeholders? ShowNotes and Episode Transcript on www.cloudsecuritypodcast.tv Twitter - @kaizenteq @hashishrajan If you want to watch videos of this and previous episodes: - Twitch Channel: https://lnkd.in/gxhFrqw - Youtube Channel: https://lnkd.in/gUHqSai
Chaos engineering is a powerful practice where experiments are run to build confidence that a system operates as expected. While the practice shapes the way that large-scale systems are built, it is underutilized in the security space. Verica, a continuous verification company that uses chaos engineering to make systems more secure, is looking to remedy this shortfall, and its co-founder and CTO, Aaron Rinehart joins us today. Aaron has been expanding the possibilities of chaos engineering in its application to other safety-critical portions of the IT domain, notably cybersecurity. In this episode, we learn more about Aaron's diverse background. Having worked as a developer before making his move into security, he understands systems intricately, giving him unique insights. We then dive into chaos engineering, the proactive approach it takes, and the intentional feedback loop it provides. Aaron believes that these experiments are great learning moments because there is not a high cognitive load that comes with unplanned system failures. After, we turn our attention to how chaos engineering ensures systems' stability is accelerated in a controlled and managed way. Along with this, we explore why it's not necessary to wait for production to test different security controls, what security chaos engineering offers instant response teams, and some fascinating use cases. Be sure to tune in today!
Napomena: kvalitet zvuka u poslednjih nekoliko minuta je lošiji, što je posledica tehničkih problema sa jednim od mikrofona. Nadamo se da ćete, i pored toga, uživati u ovoj epizodi. Danas sa Vericom Petrašinović iz EkoBlog redakcije razgovaramo o koralima i koralnim grebenima - šta su, kako i zašto bele, ali i kako to možemo sprečiti samo su neka od pitanja kojima se bavimo u novoj epizodi EkoPoda.
Co-Founder and CEO Casey Rosenthal and Co-Founder and CTO Aaron Rinehart of Verica join us today to talk Chaos Engineering and Security, Continuous Integration, Delivery, Verification, and more! Visit https://www.securityweekly.com/esw for all the latest episodes! Show Notes: https://wiki.securityweekly.com/ESWEpisode186
This week, we talk Enterprise News, to talk about how SureCloud Launches Cyber Resilience Assessment Solution, Blackpoint Cyber launches 365 Defense - a Microsoft 365 security add-on for its MDR service, Endace and Palo Alto Networks Cortex XSOAR enable accelerated forensics of cyberthreats, Zscaler acquires Edgewise Networks, WatchGuard Technologies Completes Acquisition of Panda Security, and more! In our second segment, we welcome Alyssa Miller, Application Security Advocate at Snyk, to talk about Unraveling Your Software Bill of Materials! In our final segment, we welcome Aaron Rinehart, CTO and Co-Founder of Verica, and Casey Rosenthal, CEO and Co-Founder of Verica, to talk about Security Chaos Engineering! Show Notes: https://wiki.securityweekly.com/ESWEpisode186 To learn more about Snyk, visit: https://securityweekly.com/snyk Visit https://www.securityweekly.com/esw for all the latest episodes! Follow us on Twitter: https://www.twitter.com/securityweekly Like us on Facebook: https://www.facebook.com/secweekly
This week, we talk Enterprise News, to talk about how SureCloud Launches Cyber Resilience Assessment Solution, Blackpoint Cyber launches 365 Defense - a Microsoft 365 security add-on for its MDR service, Endace and Palo Alto Networks Cortex XSOAR enable accelerated forensics of cyberthreats, Zscaler acquires Edgewise Networks, WatchGuard Technologies Completes Acquisition of Panda Security, and more! In our second segment, we welcome Alyssa Miller, Application Security Advocate at Snyk, to talk about Unraveling Your Software Bill of Materials! In our final segment, we welcome Aaron Rinehart, CTO and Co-Founder of Verica, and Casey Rosenthal, CEO and Co-Founder of Verica, to talk about Security Chaos Engineering! Show Notes: https://wiki.securityweekly.com/ESWEpisode186 To learn more about Snyk, visit: https://securityweekly.com/snyk Visit https://www.securityweekly.com/esw for all the latest episodes! Follow us on Twitter: https://www.twitter.com/securityweekly Like us on Facebook: https://www.facebook.com/secweekly
Co-Founder and CEO Casey Rosenthal and Co-Founder and CTO Aaron Rinehart of Verica join us today to talk Chaos Engineering and Security, Continuous Integration, Delivery, Verification, and more! Visit https://www.securityweekly.com/esw for all the latest episodes! Show Notes: https://wiki.securityweekly.com/ESWEpisode186
So you feel like you've got a good handle on chaos engineering...but can you use it for security use cases? Aaron Rinehart of Verica (and the author of the upcoming O'Reilly book on the topic) walks Matt and Jessica through some of the exciting ways that chaos engineering can be used for security approaches.
So you feel like you've got a good handle on chaos engineering...but can you use it for security use cases? Aaron Rinehart of Verica (and the author of the upcoming O'Reilly book on the topic) walks Matt and Jessica through some of the exciting ways that chaos engineering can be used for security approaches.
Joining us this week is Aaron Rinehart, Co-Founder and CTO at Verica. While the company remains in stealth mode Aaron provides insight into the reality of Chaos Engineering and dispels plenty of concepts that most people misunderstand on the topic.
Razmere v sodstvu, korupcija in zasebne pobude so zgolj nekatere teme, o katerih smo v oddaji »Pogovor o« govorili z dr. Verico Trstenjak. Ta je nedavno izstopila iz sodnega sveta, zato je ocenila delo tega organa. Spomnili smo jo še na besede, ki jih je dejala ob izbiranju ustavnega sodnika: »Politiki ne govorite, da podpirate strokovnjake. Podpirate jih le, če so slučajno vaši.«
Was lucky to have one of my College QB’s join me and Colby on this weeks Pod. Also another UVa Football alum and long time friend Matt Conrath stops by as well. We talk was Wahoo memories including the Dreadful 08’ Gator Bowl Loss. Thanks for everyone’s support and make sure you give us a follow on Instagram @SportsFromTheStacks --- This episode is sponsored by · Anchor: The easiest way to make a podcast. https://anchor.fm/app
Jason is joined by Paul & Alex Verica of the Stanley. They talk about their careers in the culinary world, their inspirations, their favorite restaurants in the world, and what's next in their journeys.
Paul Verica is the chef and owner of The Stanley in Charlotte, which is housed in a building built in 1937 in the heart of the Stanleyville neighborhood. The restaurant features custom millwork, pressed tin ceilings, and other historic elements. Chef Verica works closely with local farms and farmers, whose ingredients serve as the driving influence behind his menus. Host Eli Sussman joined Paul Verica at the Springer Mountain Farms campfire to chat about what he’s cooking up on the grill and what’s happening in Charlotte. HRN On Tour is powered by Simplecast.
Around 12 months ago myself and Sue Todd created the new work manifesto. It was an attempt to start the debate about simple things that we can change. You can find it on the podcast website eatsleepworkrepeat.fm.It's had a briliant response, research companies have asked to help validate it, different professions like doctors and police have been in touch asking if they can adapt it for their working. Lots of companies have told me they've been trying it out with their teams.One person contacted me and offered to share the experience and learnings of the New Work Manifesto in their team. And that was Tom Kegode. I went down one lunch time a few weeks ago to meet Tom and his team at Lloyds Bank Group. Tom is an innovations programme manager who has helped share the new work manifesto across LBG.You're going to hear discussion of various parts of the manifesto and the way that people at Lloyds are trying to make work more positive and enjoyable. Round the table were Lloyds employees Sam, Kate, Miranda, Verica, Ben, Jess, Heather, Shirley, Alastair, Dave and of course Tom himself.If you're interested in using the New Work Manifesto it all on the website, it's not copyright. Use it, change it, remix it, edit it but whatever you do please hit me on linked in or via twitter to tell me how you got on.This is the last in the series. I'll be back after the summer with a stellar list of the people who have done the best research on work, laughter, philosophy and workplace creativity.if you want to hear those episodes you're best subscribing via your podcast app.I appreciate you listening. Please do get in touch. See acast.com/privacy for privacy and opt-out information.
#Golfanyone? Well, sort of. Max and Matthew ventured out to to experience the These two episodes paint a picture of an ideal Pinehurst weekend. The evenings and afternoons consist of serious culinary treats and seminars, Posh cocktails, beer and wine but before all that, in the morning you play golf. During this culinary extravaganza we were able to catch up with a few culinary superstars; first up who explains the process of working with the chefs to create thought provoking delicious dishes. After Thierry we talked with The Godfather of Charlotte cuisine . The interview with Mr. Verica took place days before the opening of his new restaurant . Nonetheless, Chef Paul was as cool, calm and collected as only a “Don” could be. On part two we learned about the existence of an ancient that is providing some of the best sea salt in the country. Nancy Bruns of revived her family’s business and is helping chefs across the south Season their food. Finally, we got around to golf. We played golf with the #spiritguide of , Mr. . Esteban is an intriguing character, we sat down after our round at and discussed how he went from a career in the military, to finance and then co-owning a true North Carolina #graintoglass distillery. Listen, learn, golf, eat and drink! Find us on Instagram @NCFBPOD Facebook: Detailed Show notes @ Friends & Sponsors: and Hosts: & Producer: Announcer/House Voice: Music: Marketing Management:
#Golfanyone? Well, sort of. Max and Matthew ventured out to to experience the These two episodes paint a picture of an ideal Pinehurst weekend. The evenings and afternoons consist of serious culinary treats and seminars, Posh cocktails, beer and wine but before all that, in the morning you play golf. During this culinary extravaganza we were able to catch up with a few culinary superstars; first up who explains the process of working with the chefs to create thought provoking delicious dishes. After Thierry we talked with The Godfather of Charlotte cuisine . The interview with Mr. Verica took place days before the opening of his new restaurant . Nonetheless, Chef Paul was as cool, calm and collected as only a “Don” could be. On part two we learned about the existence of an ancient that is providing some of the best sea salt in the country. Nancy Bruns of revived her family’s business and is helping chefs across the south Season their food. Finally, we got around to golf. We played golf with the #spiritguide of , Mr. . Esteban is an intriguing character, we sat down after our round at and discussed how he went from a career in the military, to finance and then co-owning a true North Carolina #graintoglass distillery. Listen, learn, golf, eat and drink!
On our next episode Wesam is joined by actor, director and producer, TOM VERICA! They talk about their new Shondaland TV show on ABC, FOR THE PEOPLE, Directing, The “Machine Gun Story”, Yerba Mate, and tons of other behind the scenes goodies… enjoy!
On our next episode Wesam is joined by actor, director and producer, TOM VERICA! They talk about their new Shondaland TV show on ABC, FOR THE PEOPLE, Directing, The “Machine Gun Story”, Yerba Mate, and tons of other behind the scenes goodies… enjoy!
Folklore, Fairies, Cold Iron of Sussex and Puck of Pook's Hill This is our biggest show ever! A real MONSTER of a show with an excerpt from the fascinating book, British Witch Legends of Sussex which you can get hold of from the publisher Country Books, a great story by Rudyard Kipling all about that tricky Fey, Puck and six pieces of great Fairy-inspired music. It's all topped off by two poems - including one poem read by our 9-year old Grand-daughter, Amielia! Full show-notes, details and Contributor pages over at our main Website at http://celticmythpodshow.com/sussex Running Order: Intro 0:41 News & Views 2:05 Sussex Farms, Lore & Augury 3:10 Pica Pica by Kate Fletcher & Corwen Broch 6:17 Ecology and the 'Downs' of Sussex 9:09 Trip to Skye/Dance to your Daddy by Mike Gulston 14:15 British Witch Legends of Sussex, Pt.1 by Shaun Cooper 18:28 Celtic Tribes 23:37 Faerie Tale by Spiral Dance 24:35 British Witch Legends of Sussex, Pt.2 by Shaun Cooper 27:34 Scarborough Faire by Jenna Greene & Kellianna 39:57 All about the origins of Scarborough Fair 43:23 Cold Iron from 'Rewards and Fairies' by Rudyard Kipling 45:55 Shakespeare's Puck & Sussex Pharisees 1:21:39 Iron from Stone by Damh the Bard 1:26:00 Show Summary 1:33:56 Song of the Travelling Fairies by Kate Fletcher & Corwen Broch 1:39:57 Listener Feedback - Natasha 1:44:08 Fairies by Rose Fyleman 1:45:33 Outtakes 1:48:54 We hope you enjoy it! Gary & Ruthie x x Released: 3rd April 2017, 1hr 51m It's always great to hear from you! Email garyandruth@celticmythpodshow.com, or call us using Speakpipe News & Views We bring you up-to-date with the progress of the website updates and let you know that the Scripting for Branwen, Daughter of Llŷr, is nearing completion. We also let you know that all of our shows are now hosted on the much more secure and speedier Libsyn servers, and the Shownotes pages can also be found there. Pica Pica by Kate Fletcher & Corwen Broch Pica Pica is a song stitched together from Magpie rhymes. Fishe or Fowle is Kate and Corwen's new duo CD. It is a double CD with 25 tracks. Available now, as a physical CD from their website or to download from Bandcamp. They are musicians, instrument makers and workshop leaders who perform folk music and drama, recreate Ancient music and instruments, make crafts, run workshops for schools and demonstrate at museums and other events. You can find out more about these talented folks on their website or on our Contributor Page. Trip to Skye/Dance to your Daddy by Mike Gulston This beautiful Medley is made up by Mike's version of Trip to Skye, that he has sped up to a Mazurka rhythm and a beautiful rendition of Dance to your Daddy. He has written his own extra verse to this traditional English folk song. Mike's new solo album, Barking, was released in May 2016, an eclectic collection of traditional and modern songs, ranging from totally silly to tragic, romantic and singalong. For more details about Mike, and his work with Blanche Rowen, see their website or our Contributor Page. British Witch Legends of Sussex by Shaun Cooper The book includes over sixty Sussex witch legends, mostly in their original texts, and they are compared with witch legends from the rest of the country - so the book is essentially a comparative study of witch legends, albeit with a very strong Sussex emphasis. Other subjects covered are: Sussex fairy and Devil legends, and dragons, Roman roads, the origins and dissemination of witch legends, and so forth. You can see an interactive map of this area on Google Maps or download the KML file for Google Maps/Earth. You can find out more about Shaun and where to get hold of his book on our Contributor Page on with his Publisher, Country Books. We discuss which tribes might fall into the categories of Iron Age 'A', 'B' and 'C' Celts that are referred to in the reading. Although there are some discrepancies with the dating, the history does make sense when compared with the movements of the Atrebates, Catevellauni and Cantiaci tribes at the time of the Roman Conquest of Britain (A.d. 43). Our sources are: http://www.historyfiles.co.uk/KingListsBritain/BritainAtrebates.htm http://www.historyfiles.co.uk/KingListsBritain/BritainCatuvellauni.htm http://www.historyfiles.co.uk/KingListsBritain/BritainCantii.htm http://www.historyfiles.co.uk/KingListsBritain/BritainRegninses.htm https://en.wikipedia.org/wiki/Atrebates https://en.wikipedia.org/wiki/Verica https://en.wikipedia.org/wiki/Cantiaci https://en.wikipedia.org/wiki/Regnenses Faerie Tale by Spiral Dance Multi-award winning group Spiral Dance, based in Adelaide, has been playing rousing, high-energy music to enthusiastic audiences throughout Australia and beyond for over a decade. With a combination of haunting vocals, evocative fiddle, intoxicating guitar riffs and groovy accordion lines, underpinned with potent bass and dynamic percussion, the band presents an eclectic blend of traditional folk-rock with powerful self-penned songs and tunes. Enchanting melodies intertwine with mythical tales that are sure to captivate your soul, tease your mind and steal your heart, casting your spirit into the realms of magic and the mists of ancient time. We are privileged to bring you the evocative track, Faerie Tale from their album Magick, for our Sussex Celts Show, and you can find the lyrics on their site. You can find out more about Spiral Dance on their website or on our Contributor Page. Scarborough Faire by Jenna Greene & Kellianna Kellianna is an American Neo-Celtic singer and songwriter internationally renowned for her powerful performance of song and chant inspired by myth, magic, sacred places and ancient times. Jenna Greene, "The Greene Lady", is a weaver of musical myth and magic. With a voice that is both ethereal and soulful, she sings of ancient lore, finding wonder and following dreams. Scarborough Faire is just one of the heart-lifting traditional folk songs on the wonderful collaborative album, Traditions, by Kellianna. You can find out more about the Kellianna on her Contributor Page or more about Jenna Greene on her Contributor Page. We talk about the origins of the original Scarborough Fair and the significance of the Parsley, Sage, Rosemary, and Thyme herbs. Cold Iron from 'Rewards and Fairies' by Rudyard Kipling Rudyard Kipling was an English journalist, short-story writer, poet, and novelist. Kipling's works of fiction include The Jungle Book (1894), Kim (1901), Puck of Pook's Hill (1906) and many short stories, including "The Man Who Would Be King" (1888). His poems include "Mandalay" (1890), "Gunga Din" (1890), "The Gods of the Copybook Headings" (1919), "The White Man's Burden" (1899), and "If—" (1910). He is regarded as a major innovator in the art of the short story; his children's books are classics of children's literature, and one critic described his work as exhibiting "a versatile and luminous narrative gift". Rewards and Fairies is a historical fantasy book by Rudyard Kipling published in 1910. The book consists of a series of short stories set in historical times with a linking contemporary narrative. Dan and Una are two children, living in the Weald of Sussex in the area of Kipling's own home Bateman's. Bateman's, Sussex They have encountered Puck and he magically conjures up real and fictional individuals from Sussex's past to tell the children some aspect of its history and prehistory, though the episodes are not always historically accurate. Another recurring character is Old Hobden who represents the continuity of the inhabitants of the land. His ancestors sometimes appear in the stories and seem very much like him. The full text of Rewards & Fairies can be found on Project Gutenberg. For more details about Rudyard Kipling visit the Wiki Page or Kipling Societ's website. Shakespeare's Puck & Sussex Pharisees We discuss how Shakespeare may have heard the folklore of Puck on his travels with the Elizabethan court. The local Sussex word for Fairies, Pharisees, comes from the double plural found in the dialect - 'fairies-ies' or 'pharisees'. "Then we have 'Puck' or 'Pook', which is derived from the Saxon word 'Puca', meaning a Goblin (Smith 1956 p.74). Both modern forms are common in placenames as will be seen later in this article, but also occurs as dialect description of fairies, but not just Goblins, which are seen as mischievous or nasty fairies (Simpson & Roud 2000 p.286). 'Dobbs' or 'Master Dobbs' is a name used for a house fairy that helps with the housework. If someone has been working harder than expected, it was often said of them that 'Master Dobbs has been helping you' (Parish & Hall 1957 p.31)." [Sussexarch.org] Iron from Stone by Damh the Bard This song, Iron from Stone, is inspired by the earlier song, Scarborough Faire. Damh tells us: "Scarborough Faire is an amazing song. Such a wonderful melody and lyric that tells of all of the impossible tasks a human woman would need to achieve to be with a man from Elfland. But I began to wonder… "These wonderful folk songs have been left us by anonymous writers from years ago and have been sung ever since. But is there another story behind Scarborough Faire? What about that songwriter from years ago? What inspired them to write such a song? So I thought I would tell that story." Damh the Bard You can find his music on iTunes, or from his website, Pagan Music. He is also the voice behind Druidcast, the official podcast of the Order of Bards, Ovates and Druids (OBOD, for short) - modern day Druids. You can find Druidcast here and find out more about OBOD here. You can find out more details about Damh on his Contributor page on our website. Cold Iron by Rudyard Kipling Puck, Dan & Una "Cold Iron" is a poem written by Rudyard Kipling published as the introduction to Rewards and Fairies in 1910. In 1983, Leslie Fish set the poem to music and recorded it as the title track on her fifth cassette-tape album. Song of the Travelling Fairies by Kate Fletcher & Corwen Broch Song of the Travelling Fairies is a Manx lullaby collected in 1930 by Mona Douglas from Caesar Cashin who said that after each verse there used to be a little dance imitating the movements of the particular bird named. It comes from Fishe or Fowle - Kate and Corwen's new duo CD. It is a double CD with 25 tracks. Available now, as a physical CD from their website or to download from Bandcamp. Listener Feedback from Natasha in Portsmouth We play some Audio feedback from Natasha in Portsmouth who recommends the lovely music of Lisa Thiel. There are fairies at the bottom of our garden by Rose Fyleman, read by Amielia Rose Fyleman (1877–1957) was an English writer and poet, noted for her works on the fairy folk, for children. Her poem There are fairies at the bottom of our garden was set to music by English composer Liza Lehmann. This classic, famous and iconic poem first appeared in her book, Fairies and Chimneys, in 1917. It is read here by our 9-year-old grand-daughter, Amielia who makes her reading debut on our Show! Get EXTRA content in the Celtic Myth Podshow App for iOS, Android & Windows Contact Us: You can leave us a message by using the Speakpipe Email us at: garyandruth@celticmythpodshow.com. Facebook fan-page http://www.facebook.com/CelticMythPodshow, Twitter (@CelticMythShow) or Snapchat (@garyandruth), Pinterest (celticmythshow) or Instagram (celticmythshow) Help Spread the Word: Please also consider leaving us a rating, a review and subscribing in iTunes or 'Liking' our Facebook page at http://www.facebook.com/CelticMythPodshow as it helps let people discover our show - thank you :) If you've enjoyed the show, would you mind sharing it on Twitter please? Click here to post a tweet! Ways to subscribe to the Celtic Myth Podshow: Click here to subscribe via iTunes Click here to subscribe via RSS Click here to subscribe via Stitcher Special Thanks BertycoX, for Rain in a Desert from Film'O Graf. See the Contributor Page for details. Armolithae, for Endless Blue from Artanis and Journey from Beneath the Iron Star. See the Contributor Page for details. Kenjiakira, For all the children of the earth from Azur Requiem. See the Contributor Page for details. Julien Boulier, for Dogen Poignance from Erable and Remanence Prisme from the album Remanence. See the Contributor Page for more details. Pascal SER'JACOBS, for Realité virtuelle from the album Confusion. See the Contributor Page for more details. Keltoria, for The Gathering Storm from the album Lia Fail (Stone of Destiny) and Hollow Hills from Beyond the Wildwood. See the Contributor Page for more details. XCyril, for Max s'introduit chez Zeger et commence a fouiller from the album Alter Ego. See the Contributor Page for more details. Esgi, for Dawn of Mind, from the album Echoes in Time. See the Contributor Page for more details. Victor Stellar, for Kaleidoscope. See the Contributor Page for more details. VS, for Libera from Libera. See the Contributor Page for more details. Flavio Simone, Absence infini from Orchestrale. See his Contributor Page for more details. Adragante, for Harmonies from Harmonie Cosmique. See the Contributor Page for more details. Tolen, Free Play Music For incidental music: Diane Arkenstone The Secret Garden. See the Contributor Page for details. Kim Robertson, Angels in Disguise. See the Contributor Page for more details. Jigger, Time Ticks Away. See the Contributor Page for more details. For our Theme Music: The Skylark and Haghole, the brilliant Culann's Hounds. See their Contributor page for details. Additional Sources OBOD And, of course, the Awen - inspiration and imagination! Extra Special Thanks for Unrestricted Access to Wonderful Music (in Alphabetic order) Anne Roos Extra Special thanks go for permission to use any of her masterful music to Anne Roos. You can find out more about Anne on her website or on her Contributor page. Caera Extra Special thanks go for permission to any of her evocative harping and Gaelic singing to Caera. You can find out more about Caera on her website or on her Contributor Page. Celia Extra Special Thanks go for permission to use any of her wonderful music to Celia Farran. You can find out more about Celia on her website or on her Contributor Page. Damh the Bard Extra Special thanks go to Damh the Bard for his permission to use any of his music on the Show. You can find out more about Damh (Dave) on his website or on his Contributor page. The Dolmen Extra Special thanks also go to The Dolmen, for their permission to use any of their fantastic Celtic Folk/Rock music on the Show. You can find out more about The Dolmen on their website or on our Contributor page. Keltoria Extra Special thanks go for permission to use any of their inspired music to Keltoria. You can find out more about Keltoria on their website or on their Contributor page. Kevin Skinner Extra Special thanks go for permission to use any of his superb music to Kevin Skinner. You can find out more about Kevin on his website or on his Contributor page. Phil Thornton Extra Special Thanks go for permission to use any of his astounding ambient music to the Sonic Sorcerer himself, Phil Thornton. You can find out more about Phil on his website or on his Contributor Page. S.J. Tucker Extra Special thanks go to Sooj for her permission to use any of her superb music. You can find out more about Sooj on her website or on her Contributor page. Spiral Dance Extra Special thanks go for permission to use Adrienne and the band to use any of their music in the show. You can find out more about Spiral Dance on their website or on their Contributor page. SaveWe finish off by wishing you 'Hwyl Fawr', which is Welsh for 'Goodbye and have fun'! Save Save Save Save Save Save Save
Retired Special Agent Barbara Verica worked counter-intelligence matters for the first 15 years of her 30-year career and investigated economic crimes for the last fifteen. In this episode of FBI Retired Case File Review, Barbara Verica is interviewed about her time as an undercover operative in Manhattan gathering intelligence and the evidence needed to prove that her neighbor, a diplomat for an unidentified foreign country, was selling secrets to the former Soviet Union. Barbara also discusses an $5 million investment fraud case she investigated where in the subject of her case harassed and threatened to sue everyone involved, including a local judge and federal judge.
© 2020-2025 Ivy Podcast Discovery LLC
