Podcast appearances and mentions of damon edwards

Damon Edwards is Senior Director, Product at PagerDuty. I've been aware of Damon's impressive work in the DevOps space since my first Enterprise Technology Leadership Summit where Damon is continuously a member of the program committee. But, in the last couple of years, we've gotten to know each other better and engaged in some super interesting conversations and topics that I wanted to share with you.This time, we talked about the timeless topic of providing value and whether operations, in the broader sense, can be a competitive differentiator for a company. The conversation is as much a history lesson as it is a primer for operating in the future.✨ Please leave a review on your favorite podcast platform, your feedback is gold. ✨Did you know there is a 0800-DEVOPS newsletter? Take a look and subscribe here 0800-DEVOPS #62 – Operations as competitive advantage with Damon Edwards.Text me what you think.

In this episode Damon Edwards interviews me about my upcoming Deming book. Damon and I have been DevOps partners in crime since the beginning of DevOps. We were both down in Boca Raton recording for the Techstrong Predict conference. Techstrong let us use their facility to record the podcast. Damon does a great job of pulling knowledge about my book. 

New York Riptide defenseman Damon Edwards and Dr. Fred Opie, former pro and collegiate lacrosse star and Professor of History at Babson College, join SportsJam with Doug Doyle to talk about Lacrosse is for Everyone Night at Nassau Coliseum

This week, Jamie Dawick stops by and chats about how the move to Hamilton is going, the upcoming NLL Draft and the departure of Damon Edwards in Free Agency.

A black kid growing up playing the sport of lacrosse wasn’t exactly the norm for Damon Edwards growing up in Toronto but he found a way to make it his own. A professional lacrosse player for the Toronto Rock, Damon has spent 9+ years sprinting his was past opponents with his blazing fast speed. Oh yeah, he’s also the best looking guy in the league. Sit back, & enjoy this awesome interview while Damon talks to us a little bit about his Damon 45 programming.

In this episode, MIM founder and CEO, Adam Norman sits down with Damon Edwards from Rundeck. Damon is the Cofounder and Chief Product Officer. Damon talks about Rundeck and PagerDuty, automation in Major Incident Management and how Operations can be more efficient and remove silos.www.majorincidentmanagement.comSubscribe to the MIM® newsletterConnect with us: on Linkedinon Twitter: @major_incidentsYoutube

When Shannon Lietz and the team at DevSecOps.org published the DevSecOps Manifesto six years ago, security was uppermost in their minds. The manifesto starts with a call to arms… “Through Security as Code, we have and will learn that there is simply a better way for security practitioners, like us, to operate and contribute value with less friction. We know we must adapt our ways quickly and foster innovation to ensure data security and privacy issues are not left behind because we were too slow to change.” The effect of the DevSecOps movement was not understood by many, other than the handful of practitioners who understood what the team was going after: security is the responsibility of everyone, not just the security team. Security deserves a seat at the DevOps table. Fast forward six years, and security is now not just at the table, but sitting at the head of the table, leading the way. During this transition to focus on security, operations has become the short leg on a three legged stool. What was original a two team party, Dev and Ops, became a threesome, gradually ignoring operations as Developers and Security built a strong relationship. Damon Edwards has been my go-to person when I want to talk to someone about how operations continues to be relevant as the third part of DevSecOps. I caught up with Damon a couple weeks back to talk with him about how the transition to enterprise automation is going in the industry, what has been happening in the past year with the COVID lockdown, and what he’s looking forward to in 2021. I started the conversation, asking how he perceives his role in the DevSecOps Community. ---------- This broadcast is supported by OWASP, the Open Web Application Security Project, host of “Call to Battle” a series of events for gamers, challenge champs, and fun-nerds. Get more information at owasp.org/events… and by JupiterOne.com featuring solutions that help you “Know more. Fear less” by mapping your cyber assets and knowing the relationships between those assets.

Jayne Groll sits down with Damon Edwards of Rundeck to discuss incident management and the state of DevOps and SRE and ITIL.

One of the best parts of attending DOES 2019 in Las Vegas was meeting so many of the leaders and innovators from the world of DevOps. Damon Edwards's work is extremely well known in the DevOps field and I was lucky enough to discuss his history during this interview. Damon Edwards is a Co-Founder of Rundeck Inc., the makers of Rundeck, the popular open source Operations Management Platform. Damon has spent over 15 years working with both the technology and business ends of IT Operations and is noted for being a leader in porting Lean and cutting-edge DevOps techniques to large-scale enterprise organizations. Damon is a frequent conference speaker and writer who focuses on DevOps, SRE, and Operations improvement topics. Damon is active in the international DevOps community, a co-host of the DevOps Cafe podcast, and a content chair for Gene Kim’s DevOps Enterprise Summit. https://twitter.com/damonedwards https://rundeck.com

We’re back –live from DevOps World | Jenkins World 2019 – with a panel comprised of Jayne Groll – DevOps Institute; Helen Beal – Ranger4; Damon Edwards – Rundeck; and Sean Davis – Equifax and hosted by Sam Fell. Straight off a live panel, the group dives right into their observations on the investments companies are making in upskilling their people

Damon Edwards, Co-Founder of Rundeck, Inc., the popular open source self-service operations platform, points out how much energy in DevOps has been about activities that start in Dev and move towards Ops, seeing deployment as kind of a finish line. But what comes after deployment? Organizations seem to struggle with fundamentally transforming how they operate due to various siloed, ticket-driven, low-trust and centralized practices that have been accepted in Operations for far too long. According to Edwars, in order to align together and reach the holistic agility of speed that everybody has been looking for, we need to give Ops the same level of attention and transformation that we have on the Dev side.

Tune in to host Mike Kavis and guest Damon Edwards as they discuss how Site Reliability Engineering (SRE) works, some of the common benefits, and why it is important to define an SRE model specific to your organization. Learn how SRE’s shared responsibility model and feedback mechanisms can help organizations gain control and enable the operations, development, and business teams to work together.

When doing research around launching DevOps.com, one of the most interesting and leading figures in the DevOps movement was Damon Edwards. It has always been a goal to sit down with Damon for a DevOps Chat. While having interviewed him numerous times for DevOps TV, for this chat, Damon joins us to discuss Rundeck(https://www.rundeck.com)and how it is helping flesh out the Ops in DevOps. Damon is super knowledgeable and well versed in this and other areas, so this chat is a really informative episode. Enjoy!

When you put all of the step needed to create good software up on the board, there's a lot of them. It's a lot more than just writing code, or even writing requirements and stories. Around Pivotal, we think of this full, end-to-end process as the circle of code: Ideas → prioritization / planning → coding → deployment → runtime → monitoring → feedback, and back again. Richard and Coté discuss these steps and how organizations are starting to appreciate "the big picture." They also cover some cloud native news: Amazon buying a browser-based IDE, Cloud9; Google expanding their cloud; and Verizon's purchase of Yahoo! News AWS buys Cloud9, makers of a cloud-based IDE. Also Codenvy and the related Eclipse project. Google add West Coast cloud spot. Yahoo! And Verizon love child. Coté's collection of coverage. Main Topic "Circle of Software," Onsi's talk where he outlines this concept: Ideas → prioritization / planning → coding → deployment → runtime → monitoring → feedback, and back again What do Coté and Richard think of this model? Lots of individually popular tools at each stage of the circle … Prioritization: Jira, Pivotal Tracker, Trello, and more Coding → Java/Spring, Node, .NET, Ruby, and more. Plus countless IDEs from IntelliJ to Visual Studio Code to Spring Tool Suite. Not to mention web IDEs. Deployment → Jenkins, Concourse, GoCD, TravisCI, and more. Platform → Pivotal Cloud Foundry, cloud IaaS, containery stuff Monitoring → Datadog, New Relic, Dynatrace, and more. Log storage in Splunk and others. Feedback → Tools like UserVoice Where does friction arise in the handoffs between those stages? Damon Edwards value-stream talk from DevOpsDays Austin 2015. Is anyone currently trying to bridge the gaps? Between which stages? The marriage of tools and culture in making this work If you aren't committed to continuously delivery and using feedback to fuel the next iteration, don't waste your time setting up this machinery Also: SpringOne Platform! Aug 1st to 4th. Use the code pivotal-cote-300 for $300 off registration.

When you put all of the step needed to create good software up on the board, there's a lot of them. It's a lot more than just writing code, or even writing requirements and stories. Around Pivotal, we think of this full, end-to-end process as the circle of code: Ideas → prioritization / planning → coding → deployment → runtime → monitoring → feedback, and back again. Richard and Coté discuss these steps and how organizations are starting to appreciate "the big picture." They also cover some cloud native news: Amazon buying a browser-based IDE, Cloud9; Google expanding their cloud; and Verizon's purchase of Yahoo! News AWS buys Cloud9, makers of a cloud-based IDE. Also Codenvy and the related Eclipse project. Google add West Coast cloud spot. Yahoo! And Verizon love child. Coté's collection of coverage. Main Topic "Circle of Software," Onsi's talk where he outlines this concept: Ideas → prioritization / planning → coding → deployment → runtime → monitoring → feedback, and back again What do Coté and Richard think of this model? Lots of individually popular tools at each stage of the circle … Prioritization: Jira, Pivotal Tracker, Trello, and more Coding → Java/Spring, Node, .NET, Ruby, and more. Plus countless IDEs from IntelliJ to Visual Studio Code to Spring Tool Suite. Not to mention web IDEs. Deployment → Jenkins, Concourse, GoCD, TravisCI, and more. Platform → Pivotal Cloud Foundry, cloud IaaS, containery stuff Monitoring → Datadog, New Relic, Dynatrace, and more. Log storage in Splunk and others. Feedback → Tools like UserVoice Where does friction arise in the handoffs between those stages? Damon Edwards value-stream talk from DevOpsDays Austin 2015. Is anyone currently trying to bridge the gaps? Between which stages? The marriage of tools and culture in making this work If you aren't committed to continuously delivery and using feedback to fuel the next iteration, don't waste your time setting up this machinery Also: SpringOne Platform! Aug 1st to 4th. Use the code pivotal-cote-300 for $300 off registration.

When you put all of the step needed to create good software up on the board, there's a lot of them. It's a lot more than just writing code, or even writing requirements and stories. Around Pivotal, we think of this full, end-to-end process as the circle of code: Ideas → prioritization / planning → coding → deployment → runtime → monitoring → feedback, and back again. Richard and Coté discuss these steps and how organizations are starting to appreciate "the big picture." They also cover some cloud native news: Amazon buying a browser-based IDE, Cloud9; Google expanding their cloud; and Verizon's purchase of Yahoo! News AWS buys Cloud9, makers of a cloud-based IDE. Also Codenvy and the related Eclipse project. Google add West Coast cloud spot. Yahoo! And Verizon love child. Coté's collection of coverage. Main Topic "Circle of Software," Onsi's talk where he outlines this concept: Ideas → prioritization / planning → coding → deployment → runtime → monitoring → feedback, and back again What do Coté and Richard think of this model? Lots of individually popular tools at each stage of the circle … Prioritization: Jira, Pivotal Tracker, Trello, and more Coding → Java/Spring, Node, .NET, Ruby, and more. Plus countless IDEs from IntelliJ to Visual Studio Code to Spring Tool Suite. Not to mention web IDEs. Deployment → Jenkins, Concourse, GoCD, TravisCI, and more. Platform → Pivotal Cloud Foundry, cloud IaaS, containery stuff Monitoring → Datadog, New Relic, Dynatrace, and more. Log storage in Splunk and others. Feedback → Tools like UserVoice Where does friction arise in the handoffs between those stages? Damon Edwards value-stream talk from DevOpsDays Austin 2015. Is anyone currently trying to bridge the gaps? Between which stages? The marriage of tools and culture in making this work If you aren't committed to continuously delivery and using feedback to fuel the next iteration, don't waste your time setting up this machinery Also: SpringOne Platform! Aug 1st to 4th. Use the code pivotal-cote-300 for $300 off registration.

When you put all of the step needed to create good software up on the board, there's a lot of them. It's a lot more than just writing code, or even writing requirements and stories. Around Pivotal, we think of this full, end-to-end process as the circle of code: Ideas → prioritization / planning → coding → deployment → runtime → monitoring → feedback, and back again. Richard and Coté discuss these steps and how organizations are starting to appreciate "the big picture." They also cover some cloud native news: Amazon buying a browser-based IDE, Cloud9; Google expanding their cloud; and Verizon's purchase of Yahoo! News AWS buys Cloud9, makers of a cloud-based IDE. Also Codenvy and the related Eclipse project. Google add West Coast cloud spot. Yahoo! And Verizon love child. Coté's collection of coverage. Main Topic "Circle of Software," Onsi’s talk where he outlines this concept: Ideas → prioritization / planning → coding → deployment → runtime → monitoring → feedback, and back again What do Coté and Richard think of this model? Lots of individually popular tools at each stage of the circle … Prioritization: Jira, Pivotal Tracker, Trello, and more Coding → Java/Spring, Node, .NET, Ruby, and more. Plus countless IDEs from IntelliJ to Visual Studio Code to Spring Tool Suite. Not to mention web IDEs. Deployment → Jenkins, Concourse, GoCD, TravisCI, and more. Platform → Pivotal Cloud Foundry, cloud IaaS, containery stuff Monitoring → Datadog, New Relic, Dynatrace, and more. Log storage in Splunk and others. Feedback → Tools like UserVoice Where does friction arise in the handoffs between those stages? Damon Edwards value-stream talk from DevOpsDays Austin 2015. Is anyone currently trying to bridge the gaps? Between which stages? The marriage of tools and culture in making this work If you aren’t committed to continuously delivery and using feedback to fuel the next iteration, don’t waste your time setting up this machinery Also: SpringOne Platform! Aug 1st to 4th. Use the code pivotal-cote-300 for $300 off registration.

When you put all of the step needed to create good software up on the board, there's a lot of them. It's a lot more than just writing code, or even writing requirements and stories. Around Pivotal, we think of this full, end-to-end process as the circle of code: Ideas → prioritization / planning → coding → deployment → runtime → monitoring → feedback, and back again. Richard and Coté discuss these steps and how organizations are starting to appreciate "the big picture." They also cover some cloud native news: Amazon buying a browser-based IDE, Cloud9; Google expanding their cloud; and Verizon's purchase of Yahoo! News AWS buys Cloud9, makers of a cloud-based IDE. Also Codenvy and the related Eclipse project. Google add West Coast cloud spot. Yahoo! And Verizon love child. Coté's collection of coverage. Main Topic "Circle of Software," Onsi’s talk where he outlines this concept: Ideas → prioritization / planning → coding → deployment → runtime → monitoring → feedback, and back again What do Coté and Richard think of this model? Lots of individually popular tools at each stage of the circle … Prioritization: Jira, Pivotal Tracker, Trello, and more Coding → Java/Spring, Node, .NET, Ruby, and more. Plus countless IDEs from IntelliJ to Visual Studio Code to Spring Tool Suite. Not to mention web IDEs. Deployment → Jenkins, Concourse, GoCD, TravisCI, and more. Platform → Pivotal Cloud Foundry, cloud IaaS, containery stuff Monitoring → Datadog, New Relic, Dynatrace, and more. Log storage in Splunk and others. Feedback → Tools like UserVoice Where does friction arise in the handoffs between those stages? Damon Edwards value-stream talk from DevOpsDays Austin 2015. Is anyone currently trying to bridge the gaps? Between which stages? The marriage of tools and culture in making this work If you aren’t committed to continuously delivery and using feedback to fuel the next iteration, don’t waste your time setting up this machinery Also: SpringOne Platform! Aug 1st to 4th. Use the code pivotal-cote-300 for $300 off registration.

Our guest on the podcast this week is Damon Edwards, Founder atDTO Solutions and SimplifyOps and one of the early thought leaders in the DevOps movement. We discuss why Bimodal IT is the problem, not the solution. It is true that if technology moves too quickly an organization can lose control, but that does not mean the opposite is true and that an organization is completely safe if it moves very slowly. Large enterprises who have been successful at implementing DevOps practices include Ticketmaster, Nordstrom, and unicorn companies like Amazon who have been able to build DevOps processes from scratch as they grew.

I was able to get a quick update from Damon, Matt, Eoin and Martin this week at AppSec USA 2014 Denver. They each have a different perspective on what is going with OWASP in different parts of the world. Have a listen...

On this episode of Arrested DevOps Matt and Trevor are  joined by some of the finest minds in DevOps podcastery - Damon Edwards of DevOps Cafe and Sascha Bates of The Ship Show. The panel addresses some common beliefs on DevOps, and whether these beliefs are true...or just MYTHS.

On this episode of Arrested DevOps Matt and Trevor are  joined by some of the finest minds in DevOps podcastery - Damon Edwards of DevOps Cafe and Sascha Bates of The Ship Show. The panel addresses some common beliefs on DevOps, and whether these beliefs are true...or just MYTHS.

Demystifying DevOps: A Chat with Damon Edwards