277 Episoden
- Platform architect Thomas Schuetz explains how much Kubernetes engineers need to know. In his experience the software itself rarely broke: most of the problems he hit were ones he caused himself. We also talk about automating infrastructure end to end and building internal platforms without trapping developers in a golden cage.
In this video, we cover:
How much Kubernetes software engineers need to know when a container can run anywhere
Cloud native first principles: automate everything, tear down and rebuild clusters, and let only automation touch the cluster
Home labs and offloading AI coding agents from your laptop
Paved roads vs. golden cages: developer experience and agent experience with APIs and MCP servers
Building platforms from the applications down, and fixing platform pain through pull requests
This episode is for software engineers who deploy on a platform every day and want to understand what sits underneath it, and for platform engineers who want developers to choose their platform.
Timestamps:
00:00:00 - Intro
00:00:45 - Why His Home Lab Now Runs 24/7
00:01:48 - Teaching Kubernetes: Students vs Skeptical Companies
00:03:10 - Running AI Coding Agents in Sandboxes and Home Labs
00:05:05 - The #1 Cloud Native Rule: Automate Everything
00:07:30 - Tearing Down and Rebuilding Clusters Every Day
00:09:10 - Why Kubernetes Rarely Broke for Him
00:10:14 - How Much Kubernetes Should Software Engineers Know?
00:12:53 - Why People Think Kubernetes Is Too Complex
00:15:29 - How to Learn Kubernetes Without Getting Overwhelmed
00:17:37 - Handling the Pressure of Infrastructure at Scale
00:19:59 - When a Golden Path Becomes a Golden Cage
00:25:43 - Designing Platforms for AI Agents With APIs and MCP
00:27:54 - Build Platforms From Applications, Not the Tool Landscape
00:32:05 - Will AI Agents Turn Every Developer Into an Architect?
00:35:29 - Platform Pain? Open a Pull Request
Guest: Thomas Schuetz, Cloud Native Architect
https://www.linkedin.com/in/thschue
#Kubernetes #PlatformEngineering #SoftwareEngineering - What do coding agents need from engineers to be trusted? AI consultant Fausto Albers builds production software with agents and doesn't believe anyone still reads the code line by line. Here is what he relies on instead.
We cover:
Why newer models are "eating the harness", and the shift from context engineering to loop engineering
The state a coding agent should be in before it runs for hours, and the gates its output has to pass
Observability with open-source MLflow when you can't read every trace
A shared ontology and a three-layer memory stack: a Karpathy-style Markdown wiki in Obsidian, graph memory and a local vector database in Docker
Disposable vs durable software, and why software built by intent threatens traditional SaaS
Why AI makes attacks cheaper than defense
This episode is for software engineers and tech leads who want to give coding agents real autonomy without giving up responsibility for what gets built.
Timestamps:
00:00:00 - Intro
00:00:49 - Why Newer Models Keep Eating the Harness
00:02:26 - Will SaaS Survive the Next Ten Years?
00:03:39 - From Sociology to Cocktail Bartender to Restaurant Owner
00:07:19 - Why Human Preference Can't Be Reduced to Data
00:10:10 - What I Learned From a Failed Restaurant Chatbot
00:14:16 - Learning Faster With AI and Who Gets Left Behind
00:18:38 - What State Should Your Coding Agent Be In?
00:22:09 - Building a Shared Understanding Before Kicking Off a Loop
00:26:58 - Why Nobody Really Reads AI Code Line by Line
00:31:34 - The Real Reason Engineers Push Back on AI
00:33:48 - Sloppy, Disposable or Durable: How to Judge Code
00:35:18 - A Three-Layer Memory System for Coding Agents
00:39:44 - Why Domain Experts Matter When Execution Gets Cheap
00:42:23 - How AI Makes Attacks Cheaper Than Defense
Guest: Fausto Albers, AI consultant at Wonder Why
https://www.linkedin.com/in/stepintoliquid
#codingagents #softwareengineering #aiagents - What is the most future-proof engineering skill to learn now with AI and Coding agents? Time is up for traditional development cycles as Agents shrink vulnerability exploit windows from 200 days to just 18 hours.
In this video, IBM HashiCorp Field CTO Anna McDougall shares why brilliant engineers have been avoiding the single most resilient career path in tech and how it's time to change that. It's now part of what software engineering is becoming:
Why 20% of software engineers are grieving hands-on IDE coding (and why manual code is becoming like carpentry)
The #1 future-proof engineering specialty that protects your career as AI agents write more code
How to stand out in interviews using the "Pumpkin" CV strategy, high-signal personal achievements, and human networking
Why non-deterministic coding agents ignore skills.md files and why 88% of breaches come down to credentials
How engineering leaders can implement deterministic runtime guardrails, workload identity, and scoped credentials at scale
Whether you are looking to future-proof your career or a software engineer navigating agentic workflows, you will walk away with a clear roadmap for what comes next.
This episode was recorded at TechLead Conference. Join for the next edition of the event in Amsterdam on May 20: https://techleadconf.com
Guest - Anna Mcdougall:
https://www.linkedin.com/in/annajmcdougall
Timestamps:
00:00:00 - From 200 Days to 18 Hours: Why Time Is Up
00:00:47 - What a Field CTO Actually Does Every Day
00:03:53 - Why 20% of Engineers Are Grieving Hands-On Coding
00:06:55 - Why Hand-Crafted Code Is Becoming Like Carpentry
00:08:26 - The Most Future-Proof Engineering Skill Nobody Wants
00:10:53 - How to Network by Becoming the Connective Tissue
00:13:55 - How to Stand Out When AI Writes Every Resume
00:18:31 - The "Pumpkin" Strategy to Be Remembered in Interviews
00:22:25 - Why Brilliant Engineers Avoid This Career Path
00:26:42 - Why Skills Files Are Not Enough for Coding Agents
00:31:10 - Building Deterministic Guardrails Without Slowing Teams
00:36:32 - Finding Your People in Engineering Leadership
#SoftwareEngineering #CareerAdvice #AIEngineering - Meta Staff Engineer Sajal Rustagi reveals what Staff Engineers do that most don't and what the best engineers do differently to reach the top. While foundational behaviors like proactivity and ownership still separate growing engineers from stuck ones, leveling up today requires a completely new set of staff skills built around agents.
In this video, we cover:
The behavioral shift from IC4 and IC5 (Senior) to IC6 (Staff Engineer) at Meta
How top engineers treat on-call firefighting as a system-wide ownership opportunity
Why rotating between Engineering Manager (EM) and Staff IC sharpens your business and technical influence
Transitioning from Developer Experience (DX) to Agent Experience (AX) using MCP, Claude, and markdown context
This conversation is for software engineers, senior ICs, and tech leads who want to learn the new staff skills required to multiply their impact and get promoted now.
This episode was recorded at TechLead Conference, a conference for engineering leaders on adopting AI.
Timestamps:
00:00:00 - The New Staff Engineer Skills
00:00:44 - 2 Behaviors That Separate Mediocre and Staff Engineers
00:02:16 - How the Best Engineers Build an Ownership Mindset
00:04:26 - What Staff Engineers Do Differently During On-Call
00:06:26 - Senior vs. Staff Engineer: Expanding Your Sphere of Influence
00:09:56 - Why Switching Between Manager and Staff IC Builds Better Engineers
00:14:04 - Why Unblocking Engineers Now Means Unblocking Agents
00:16:41 - Managing Multi-Agent Handoffs Without Losing Control
00:19:02 - Shifting from Developer Experience to Agent Experience
00:21:47 - Why the Empty Engineering Backlog Is Still a Myth
00:25:03 - How to Build Custom Agent Workflows and Reusable Skills
00:28:31 - The #1 New Skill Software Engineers Must Build Today
00:31:10 - How Meta Engineering Culture Compares to Startups
Guest - Sajal Rustagi, Staff Engineer at Meta: https://www.linkedin.com/in/sajalrustagi
#StaffEngineer #SoftwareEngineering #EngineeringLeadership - How do senior engineers use coding agents on prod infrastructure when “make no mistakes” is just a polite request? Kerim Satirli (HashiCorp, an IBM company) explains why prompt rules don’t hold in production, and what he runs instead.
In this video, we cover:
How Infrastructure as Code (Terraform, Contentful, Datadog, Okta, Cloudflare providers) evolved from open-source PRs to automated agent harnesses
Why AI skills files and “make no mistakes” prompts are only requests, and what replaces them in production pipelines
How AI-generated pull requests are overwhelming open-source maintainers (and why projects like cURL are pushing back)
Personalized “software factories”, spec-driven development (GitHub Spec Kit), and cutting AI documentation noise with BLUF (Bottom Line Up Front)
What open-source Rust clones of Adobe mean for the future of SaaS
For infrastructure engineers, DevOps practitioners, and software architects who want to move past one-shot prompting and run coding agents on production infrastructure without losing control.
Timestamps:
00:00:00 - Why “Make No Mistakes” Is a Polite Request
00:00:38 - How Open Source Terraform Changed Provisioning
00:01:59 - Why API-First Services Matter Beyond AWS and Azure
00:04:19 - How AI Agents Changed Terraform Provider Updates
00:07:03 - Why “Make No Mistakes” Won’t Stop Your Agent
00:10:31 - Bringing Determinism Back to Agentic Workflows
00:13:07 - How AI Pull Requests Are Overwhelming Open Source
00:15:41 - Why Every Engineer Is Building a Software Factory
00:18:52 - Why AI-Generated Documentation Slows Down Humans
00:23:12 - Using Agents to Filter Noise and Summarize Specs
00:27:02 - Escape Hatches for Automated Terraform Applies
00:29:03 - Where the Joy in Engineering Lives Now
00:31:24 - Spec-Driven Development and the Return of Architecture
00:34:51 - Open-Source Rust Clones, Reverse Engineering, and SaaS
00:38:19 - How to Build Software Products People Actually Want
Guest: Kerim Satirli, Senior Developer Advocate at HashiCorp, an IBM company.
https://www.linkedin.com/in/ksatirli
#Terraform #CodingAgents #DevOps
Weitere Technologie Podcasts
Trending Technologie Podcasts
Über Beyond Coding
For software engineers ready to level up. Learn from CTOs, principal engineers, and tech leaders about the skills beyond coding: from technical mastery to product thinking and career growth. Created by Patrick Akil. Powered by Xebia
Podcast-WebsiteHöre Beyond Coding, Darknet Diaries Deutsch und viele andere Podcasts aus aller Welt mit der radio.de-App

Hol dir die kostenlose radio.de App
- Sender und Podcasts favorisieren
- Streamen via Wifi oder Bluetooth
- Unterstützt Carplay & Android Auto
- viele weitere App Funktionen







































