This is a guest conversation episode of Ship It Weekly, separate from the weekly news recaps.
In this Ship It Conversations episode, I talk with Ned Bellavance of Ned in the Cloud about DevOps beyond the buzzwords, platform engineering, infrastructure as code, AI, and why fundamentals still matter even as the tools change.
Ned is the founder of Ned in the Cloud and host of the Day 2 DevOps podcast, with more than 20 years in IT across systems administration, cloud, architecture, automation, and technical education.
We start with a problem a lot of teams run into: adopting the ceremonies of DevOps without actually adopting the principles. Standups, sprints, pipelines, and tooling can make an organization look mature, but the real goal is better communication, faster feedback loops, and delivery tied to actual outcomes.
We also talk about how teams decide what to prioritize next. Security, reliability, performance, FinOps, and platform work can all matter, but chasing whatever is newest does not help if the basics are still broken.
A big part of the conversation is where infrastructure as code goes from here. We get into Terraform's state and scaling model, API rate limits, the Terraform/OpenTofu split, Terragrunt, and newer approaches like Swamp from System Initiative. AI is making infrastructure code cheaper to produce, but understanding the architecture behind that code is becoming more valuable.
That leads into learning and career development. We talk about why networking, Linux, databases, security, cloud architecture, and troubleshooting still matter, even if an LLM writes most of the syntax. Build things, get them wrong in controlled environments, troubleshoot them, and learn what is happening underneath the abstraction.
The big takeaway: tools will keep changing. Judgment, architecture, troubleshooting, and understanding the systems underneath them are much harder to automate away.
Highlights
• Why DevOps ceremony is not the same as DevOps principles
• How teams should decide what platform work actually matters
• Why basic security hygiene still matters
• Where Terraform's current state model starts to hit limits
• Terraform, OpenTofu, Terragrunt, and the future of infrastructure as code
• How AI changes the value of writing infrastructure code
• Why architecture and troubleshooting skills become more important
• Why breaking things in controlled environments is one of the best ways to learn
Links
Ned in the Cloud: https://nedinthecloud.com
Day 2 DevOps: https://day2devops.com
Ned in the Cloud on YouTube: https://www.youtube.com/c/NedintheCloud/
Ned Bellavance on LinkedIn: https://www.linkedin.com/in/ned-bellavance/
Swamp: https://swamp.club
Terraform: https://developer.hashicorp.com/terraform
OpenTofu: https://opentofu.org
More episodes and show notes: https://shipitweekly.fm
On Call Brief: https://oncallbrief.com
