Hello, everyone. My name is Rebecca Parsons. I'm one of your co-hosts here on the ThoughtWorks

Technology Podcast, and I'm here with another one of my co-hosts, Neil Ford.

Hello, everyone. Welcome to the ThoughtWorks Technology Podcast. And today we have one of our

colleagues joining us who knows all about

Infrastructure's Code. In fact, he knows so much about it. He's written two volumes or two versions of a book,

Volume 1 and the second edition of Infrastructure's Code, our colleague based in the UK, Keith Morris.

Hello, Keith. Hi, Neil. Hi, Rebecca. Thanks for helping me on.

And so you can guess what we're going to talk about today is Infrastructure's Code, which is what

Keith has been working on the last little while. So, Keith, let's get the basics out of the way.

How would you define infrastructure as code? Why is this interesting? Yeah, okay. There's kind of like several

there's several answers to that. Like, why is it interesting? Why is it interesting to me?

I've kind of like bounced across software development and systems administration roles,

you know, going back, I don't know, 25 or more years now. So it always seemed like a natural

thing to me to try to like figure out how to like write scripts and code or whatever to,

to make the jobs of system administration easier. The way I define infrastructure as code,

clearly that it's about using code to define your infrastructure, but it's more than that.

The way I think about it is about how can we then use tools and practices and patterns and so on from

software engineering and apply that to our infrastructure. And then obviously, you know, us being,

having that kind of agile

ways of thinking about engineering and stuff, it's, it seems a natural thing to try to apply

that then to infrastructure, like how do we do test driven development? How do we do continuous

delivery? How do we do even things like microservices and so on?

...