How to change a codebase in production

UPcoming Panel discussion

How to change a codebase in production

A flexible codebase is a good one, especially in the age of AI-assisted development.

Dave Farley, Jennifer Riggins and Heidi Waterhouse

Date & time

17:00

Register for the panel discussion

Login or join LeadDev.com to view this content

Create an account to access our free engineering leadership content, free online events and to receive our weekly email newsletter. We will also keep you up to date with LeadDev events.

We have linked your account and just need a few more details to complete your registration:

First name Last name Job title Company Country

Terms and conditions I agree to the LeadDev.com terms and conditions of use

Create a password

As Dave Farley, godfather of continuous delivery, put it, “The only definition of quality in code that makes any sense is our ability to change the code.”

So what do you have to do to make sure software is always releasable? And then how do you make sure that changing in production doesn’t break production?

Caution around making changes is slowing you down. And if you didn’t have continuous delivery pipelines, guardrails, and golden paths before AI, you simply can’t safely keep up.

Join this panel discussion to:

Ensure that a change to the deployment process is treated with the same rigor as a change to the application code
Maintain a software bill of materials and clear ownership and provenance at the speed of AI
Onboard AI agents like a person in your software delivery lifecycle