AI-Native Software Delivery

Chapter 1. Introduction

A Note for Early Release Readers

With Early Release ebooks, you get books in their earliest form—the authors’ raw and unedited content as they write—so you can take advantage of these technologies long before the official release of these titles.

This will be the 1st chapter of the final book. There is no GitHub repo at this time.

If you have comments about how we might improve the content and/or examples in this book, or if you notice missing material within this chapter, please reach out to the editor at [e-mail].

Most software development teams have war stories of deployments gone wrong. These are the stories that put us on paths to modernize our delivery practices. Our deployments might include weeks or months of feature work and extensive refactoring. Developers, operations team members, a coterie of managers, and maybe a number of executives, gather in a conference “war” room. Up to this point, there has been minimal collaboration between development and operations. However, now these two groups are working together as a single team. The team starts ticking through a long checklist or playbook of manual steps.

But even exhaustive checklists do not guarantee a trouble free deployment. Given the number of changes in the release, the deployment is likely complex and risky. The team might find that a key dependency was missing from the Production environment. The team might discover that an incompatible library version was installed, or that ...