What is software delivery? There are a lot of approaches to this subject- what does “software delivery” mean at PagerDuty?
What is your idea of “best” way to deliver software, or line of best fit?
What gets in the way of companies or individuals delivering software?
-How do you mitigate and test for problems introduced by code changes? -Deployments? -Dependency issues? -External factors?
What are some patterns and anti-patterns for consistent software delivery?
On system rollback and totalised fields by Mark Burgess
I am a system administrator with PagerDuty. Along with rest of our team, I try to design systems that can withstand major outages. Before joining PagerDuty, I worked at Google, ThoughtWorks etc, where I was working with private build/deployment cloud, also enabling continuous delivery & cloud adoption. I did my masters in Life Science (Bioinformatics), and I always try to create infrastructure like living systems.
Matt Stratton is a Staff Developer Advocate at Pulumi and the global chair of the DevOpsDays set of conferences.
Matt has over 20 years of experience in IT operations and is a sought-after speaker internationally, presenting at Agile, DevOps, and cloud engineering focused events worldwide. Demonstrating his keen insight into the changing landscape of technology, he recently changed his license plate from
He lives in Chicago and has three awesome kids, whom he loves just a little bit more than he loves Diet Coke. Matt is the keeper of the Thought Leaderboard for the DevOps Party Games online game show and you can find him on Twitter at @mattstratton.
Coming from a background in .NET Software Development and consulting, he has worked with several large multinational organizations to help kick start their journey to the cloud and the world of DevOps practices and principals. He is excited to engage in new experiences, and learning opportunities.
Trevor enjoys having hearty discussions about DevOps as well organizational change and transformation.