Listen

Description

Talking with Bryan Finster, Software Engineer at Defense Unicorns and core team member of minimumcd.org, about what Continuous Delivery really is; and what's not.

00:00 Spontaneous Start and Introduction

00:13 Defining Continuous Delivery

01:28 Brian's Background in Continuous Delivery

03:44 Challenges and Misconceptions in Continuous Delivery

07:35 Automation in Continuous Delivery

12:44 Deployment Strategies and Best Practices

17:10 Real-World Examples and Industry Practices

29:03 The Importance of Simplicity and Standardization

35:36 Understanding the KISS Principle

35:43 Service-Oriented Architecture Misconceptions

36:40 Designing for Continuous Delivery

37:24 The Importance of Domain-Driven Design

37:58 Challenges in Continuous Delivery

43:31 Code Reviews and Pull Requests in CD

44:24 The Role of Testing in Continuous Delivery

45:53 The Value of Continuous Integration

48:54 Common Pitfalls in Software Development

01:03:11 The Importance of Maintainability

01:05:05 Wrapping Up and Final Thoughts

Links:

https://minimumcd.org/https://bdfinst.medium.com/

Books:

Modern Software Engineering: Doing What Works to Build Better Software Faster

Continuous Delivery: Reliable Software Releases through Build, Test, and Deployment Automation



This is a public episode. If you'd like to discuss this with other subscribers or get access to bonus episodes, visit blog.adrianstanek.dev/subscribe