Jul 1, 2026 · 48 min · 12 segments
Malcolm Matalka joins William and Eyvonne to challenge the narrative that Infrastructure as Code (IaC) is dead. Malcolm argues that the real value of IaC was never the syntax, but state and…
Malcolm MatalkaGuestWilliam CollinsHost
Eyvonne SharpHostSo one thing specifically I think in your book your background like i think you know uh you've got years of like git ops style like automation just kind of like on top of the you know terraform uh has this given you like working in this type of workflow is it kind of giving you a a ground level view and i'd like to understand that like if Your conversations with companies that have really hit that point where it breaks for teams, you know, so starting off small, you get bigger, this, you know, JSON files and things get bigger and bigger and bigger.
So, you know, what is your experience on just kind of like where this begins to break down in the first place?

Yeah, so if you take our first episode together, where we talked a lot about OCaml, a very niche programming language, the theme here is I will continue to be weird and say that I see best practices, I'm probably like the most vehemently against them and think they're just kind of stupid.

And What are those best practices? Well, when your state grows, so I'm sure most people listening are like aware of how Terraform works, but just like a quick reminder, you have what's called the root module, where is where you define all of the infrastructure that you want to manage inside of that particular unit.

And that root module has a state file and that state connects all of the identifiers in your cloud to your code.


And there's also information that you as a programmer want to define and information that the cloud wants to define.

The challenge becomes when you grow in a few ways, both in the amount of resources that you want to manage, but also in the amount of team members that you want operating on those resources.

But once you start having multiple people operating on it, now you're in the distributed systems world.

And you need a way to manage access to that CLI because only one person can be performing an operation at any single time.

And that's because that state we talked about is managed as one single blob.

And there's no real way to say two people wanting to do an operation and they get their own blob and then combine them.

So we have to serialize access, basically a big file lock and say this person gets to do this.

So that becomes a real issue at scale, both in terms of you have lots of teams, you have lots of people and you have lots of resources because more resources means things take more time.
So one thing specifically I think in your book your background like i think you know uh you've got years of like git ops style like automation just kind of like on top of the you know terraform uh has this given you like working in this type of workflow is it kind of giving you a a ground level view and i'd like to understand that like if Your conversations with companies that have really hit that point where it breaks for teams, you know, so starting off small, you get bigger, this, you know, JSON files and things get bigger and bigger and bigger.
So, you know, what is your experience on just kind of like where this begins to break down in the first place?

Yeah, so if you take our first episode together, where we talked a lot about OCaml, a very niche programming language, the theme here is I will continue to be weird and say that I see best practices, I'm probably like the most vehemently against them and think they're just kind of stupid.

And What are those best practices? Well, when your state grows, so I'm sure most people listening are like aware of how Terraform works, but just like a quick reminder, you have what's called the root module, where is where you define all of the infrastructure that you want to manage inside of that particular unit.

And that root module has a state file and that state connects all of the identifiers in your cloud to your code.


And there's also information that you as a programmer want to define and information that the cloud wants to define.

The challenge becomes when you grow in a few ways, both in the amount of resources that you want to manage, but also in the amount of team members that you want operating on those resources.

But once you start having multiple people operating on it, now you're in the distributed systems world.

And you need a way to manage access to that CLI because only one person can be performing an operation at any single time.

And that's because that state we talked about is managed as one single blob.

And there's no real way to say two people wanting to do an operation and they get their own blob and then combine them.

So we have to serialize access, basically a big file lock and say this person gets to do this.

So that becomes a real issue at scale, both in terms of you have lots of teams, you have lots of people and you have lots of resources because more resources means things take more time.
The rest of this transcript — segmented and speaker-labeled, so you land on the exact moment something was said
Search every transcript — by keyword, by phrase, or by meaning, across every show Radar indexes
Trends — what is surging across podcasts, measured against its own baseline
Alerts — when a name you follow appears in a newly indexed episode
No account is needed to search Radar.