Google Cloud's DevOps Research and Assessment (DORA) team operationalize the Accelerate State of DevOps Report, surveying over 32,000 professionals worldwide in the DevOps industry.  Dave Mangot joins the show today to share how he leverages these metrics to improve companies within their technology organizations.  

In this episode…

1. DORA metrics
2. Speed and quality 
3. Monoliths vs. microservices
4. Uptime and failure rates
5. Mean time to recover 
6. Deployment frequencies
7. Production monitoring

Jonathan shares about the new job offer he received and the progression we went through to navigate the process.  Jonathan, Will, and Jillian also discuss the various aspects of the current DevOps job market, starting a new job, and how you can grow in your career.

In this episode…

1. Stack overflow and blogposts 
2. What do you do when you first start?
3. Contracting gigs
4. Social life in the workplace vs. financial transaction
5. Single points of failure 

Today on the show, Will talks about his latest project, Trustified.io and the steps he is considering to make it DevOps ready. Will and Jonathan discuss creating the dev environment, standardized logging, CI/CD, health checks, standardized reporting dashboards, configuring the app, database migration tools, user management, and ORMs.

Elements to Make an App DevOps Ready:

1. Creating the dev environment
2. Standardized logging
3. CI/CD
4. Health checks
5. Prometheus
6. Standardized reporting dashboards
7. Configuring the app
8. Database migration tools
9. User management
10. ORMs

An anti-pattern is a pattern that you use to fix a short-term problem at the expense of your long-term goals. The insidious thing about anti-patterns isn't that they don't work or fail outright, but that they work in the short term while causing long-term failure and pain. Today on the show, Jonathan, Jillian, and Will discuss the various anti-patterns and cargo culting in software engineering, including password management, team structures, mean time to recover, and docker files management.

In this episode…

1. What is cargo cult software engineering?
2. Favorite anti-patterns
3. Password management
4. Team structure and silos
5. Mean time to recover
6. Docker files management

Today on the show, Will and Jonathan discuss deployment strategies, including rolling strategy, blue-green patterns, canary deployments, feature flags, and progressive delivery. They also discuss backward compatibilities and rollback and rollforward deployment strategies, plus share their current picks of the week.

In this episode…

1. Kubernetes orchestration
2. Blue-Green deployment patterns
3. Canary deployments
4. Feature flags
5. Progressive delivery
6. Backward compatibility
7. Rollback deployment
8. Rollforward deployment

Imagine being able to program the cloud and bridge the Dev and Ops divide with cloud. Pulumi is a universal infrastructure as code platform that allows you to build, deploy, and manage modern cloud applications using familiar languages, tools, and engineering practices. Today, Jonathan and Will discuss all the ins and outs of Pulumi.In this episode…

1. What is Pulumi and how does it work?
2. Is Pulumi replacing tools such as Ansible, Chef, Terraform altogether?
3. What is the learning curve?
4. What languages is Pulumi limited to?
5. When would you not use Pulumi?
6. What are the processes for implementation?

Do I need to learn how to write code? What are the types of program languages required in DevOps? What are the pros and cons of each? Will, Jonathan, and Jillian discuss the progressions through programming languages and their insights and opinions with each. Learn about Bash, Go, Perl, Python, Python 2, Python 3, JavaScript, Node.js, Rust, Ruby, and Java. At the end, they provide their final concluding thoughts and share their top picks.

How do you align engineering outcomes to business goals? On the show, Hersh Tapadia, Adam Dahlgren from Allstacks talk about value stream intelligence and how you can generate guiding insights for product stakeholders across engineering projects and tools so you can shape better outcomes and deliver stronger value. In this episode…

1. “Metrics are just table stakes”
2. Metrics vs feelings driven management 
3. How to evolve the conversation from data collection to value creation
4. Understanding the why behind the work to retain engineers 
5. The “dining table problem”
6. How do engineering teams respond to this approach?

Enjoy this philosophical conversation around building code more responsibly and how ethics and accountability is to be integrated into the DevOps industry. Eric Tank joins the show and shares his perspective on how to “develop for deprecation”. Building a code that is documented, tested, monitored, and deployed is important, but can you easily pass it off to someone else, or be able to walk away from the code it entirely? Johnathan joins by saying that “software is never done until it's deleted.” They finish the discussion referencing apprenticeship models and how accountability in this way could parallel other industries.

Have you considered the significance of infrastructure as code and its importance in the industry? Will, Jillian, and Jonathan deep dive into this topic, plus discuss Amazon CDK and current frameworks and tools for the best workflows.