Continuous delivery

But I find that, uh, DevOps is pretty much the same way.

I remember back in, I guess it was about twenty ten when Jez Humble and Dave Farley wrote their book, Continuous Delivery, which really popularized that idea, which my team had already been doing.

They asked me to be a technical reviewer on that book, and I said, "Well, gosh, I mean, although I work on the pipelines and I, I work closely with our operations guy, it's not my area of expertise.

I shouldn't be a technical editor." And they said, "No, no.

Uh, so it's all about just doing the best job that we can do.

Yeah.

So, um, the book you mentioned, Continuous Delivery, like, is, uh, I think it's one of those books, um, similar to some of the books you've written, Kent Beck's written, that kind of just seem to, as technology changes and all of that, the book still stays incredibly relevant.

Um, and I...

Really, that's the, the end goal that we're after here.

As always, if you enjoyed this episode, you can find us on, on YouTube, like and subscribe, or your audio podcast provider of choice by searching for Continuous Delivery Office Hours.

And until the next time, happy deployments, everyone.

Thank you, everyone.

Uh, so I've been a developer for 30 years, um, mostly poorly.

Um, uh, you know, I've been, uh, I managed to get a chance to fix that when we were given the opportunity to try to, to figure out continuous delivery at, at Walmart back in 2015.

Took it seriously and learned a whole bunch of stuff along the way.

That's mostly a people problem.

Mm-hmm.

Um, and then, so then how do I handle, you know, the, the-- there's, there's problems with its...

You know, it would go delete tests I didn't want it to, or it would, um, you know, write terrible code, and I was like, "Okay, well, how do I handle that? Is the tool bad, or do I need to add validations in my pipeline?" And so when I talk about a continuous delivery pipeline, I'm not talking about everything that happens post-commit, okay?

Yeah.

So I'm going to go to the store.

I'm going to search for a book called Continuous Delivery.

When I find it, I'm going to put it in my shopping cart.

Then I'm going to go to the checkout, pay for the book, and now I own the book.

There are processes for that.

For example, when people build really critical systems, like if you want to go to space, you'd better communicate all the assumptions to everybody concerned with them.

Sorry, I'm a hardline continuous delivery guy, and I'd slightly disagree with that.

So certainly that's where it ended up in some parts.

And I'm sitting beside a desk, and they're just like normal people doing... you know, answering their email, but I'm, like, so happy just to be hanging around with them.

But one of, one of my colleagues was a guy called Jez Humble, and Jez had written a seminal book in the software space called Continuous Delivery with David Farley, um, a couple of years earlier, and he was sort of looking for the next thing.

Um, and then I was working in ThoughtWorks introducing a lot of these, uh, methods.

Um, I'd s- I'd let go of engineering.