In this episode we unpack what containers actually are (and why “done properly” they’re small, portable, and predictable), why container images reduce the classic “works on my machine” failure mode, and a question that matters once you’re operating at scale: is Kubernetes really the orchestrator — or is it being orchestrated by everything around it?

We cover:

• Containers vs VMs (what you’re really shipping)

• Images, immutability, and repeatable deployments

• How “same artefact everywhere” changes DevOps workflows

• The Kubernetes orchestration debate (and what it implies for platform teams)

In this episode of DevOps Unpacked, Matt sits down with Christina (VP of Strategic Initiatives at Cortex, former founding engineer) to unpack what an Internal Developer Platform (IDP) actually is — and why CIOs/CTOs are using IDPs, service catalogues, and guardrails to improve delivery speed without increasing reliability and compliance risk.

You’ll learn how high-performing teams turn platform engineering into an executive lever:

• Service catalogues as an ownership and accountability system (not “another tool”)

• Golden paths (“paved roads”) to standardise delivery and reduce cognitive load

• Guardrails that enable autonomy while controlling operational and security risk

• The metrics that matter: DORA, MTTR, and SLOs (and how to use them for decision-making)

• What changes when AI starts writing code: hallucinations, policy, and practical AI coding guardrails

• CI/CD + observability as the backbone for safe, repeatable delivery and faster recovery

If you’re leading a platform/modernisation programme this year, this episode helps you separate signal from hype — and gives you the questions to ask your teams and vendors.

If you’re putting LLMs anywhere near production ops, you need guardrails. In this episode of DevOps Unpacked we break down how AI fails in real systems (hallucinations, prompt injection, and data leakage) and what to do about it.

We cover practical defences: treating prompts and retrieved text as untrusted input, using RAG safely (scoping and access control), least-privilege tool access for agents, keeping secrets out of prompts, and adding auditability + evals so your controls don’t rot over time.

AI can write code. That doesn’t mean it can run production.

In Episode 3, we break down what AI actually changes in DevOps and software engineering — and what stays stubbornly human: requirements, judgement, risk, guardrails, and the messy reality of pipelines and production systems.

We cover:

• Why “AI will replace engineers” is the wrong question

• Where AI genuinely saves time in day-to-day DevOps work

• Why requirements and review matter more (not less) with AI

• CI/CD, evidence, and the controls AI can’t shortcut

• The junior vs senior impact: how teams and careers shift

Chapters:
00:00 AI won’t kill software engineering
03:30 AI as a force multiplier
07:00 Tools vs real understanding
10:30 Requirements still matter
14:00 Pipelines and real-world constraints
18:00 Frameworks and guardrails
22:30 Safe AI in production
27:30 Where AI actually saves time
32:30 AI in daily workflows
37:00 Skills that matter more with AI
41:30 Junior vs senior impact
46:00 Long-term team impact
50:30 Engineers aren’t going anywhere

If you work in DevOps, Platform Engineering, SRE, or you’re building software that has to pass audits and survive incidents — this one’s for you.

In this episode of DevOps Unpacked, we tackle the crucial differences between CI CD, continuous integration, and continuous delivery. 🤔 Join us as we explore how tools like Jenkins and GitHub Actions enhance the CI CD pipeline, ensuring smooth deployments. Don't miss out on this essential guide to mastering devops concepts! 🚀

The conversation delves into the essence of DevOps as a culture and the role of a DevOps engineer within that culture. It explores the origins, evolution, and practical implications of DevOps, addressing misconceptions and variations in DevOps engineer roles. The discussion also covers CI/CD, GitHub Actions, Jenkins, testing, and the expanding scope of DevOps to include various disciplines. Additionally, it provides insights into the path to becoming a DevOps engineer and the skills and traits required for success in this role.

Takeaways

• DevOps is a culture
• DevOps engineer is a role within the DevOps culture

Chapters

• 00:00 Introduction to DevOps and Misconceptions
• 06:34 The Problems DevOps Seeks to Solve
• 12:38 DevOps as a Culture and Its Practical Implications
• 21:19 Understanding GitHub Actions and Jenkins in DevOps
• 31:19 Evolution of Testing in DevOps
• 36:36 Expanding Scope of DevOps: Incorporating Various Disciplines
• 44:04 Skills and Traits of a Good DevOps Engineer