Developer Productivity, Platform Engineering & Architecture with Dennis van de Laar
Released Wednesday, January 24th 2024·46 min
Show notes
About this episode
In this episode, Dennis and I and discusses his transition to Microsoft, the impact of developer productivity, and the evolution of the architect's role in tech. Tune in for insights on creating value in cloud-native technology and navigating the balance between autonomy and structured platform engineering.
Connect with Dennis van de Laar:
https://linkedin.com/in/dennis-van-de-laar-0374b4
References:
Pace-layered Application Strategy - https://www.gartner.com/en/information-technology/glossary/pace-layered-application-strategy
Jim Wilt - Five Pillars of IT Architecture - https://iasaglobal.org/Services/Public/TOPICS/Iasa_Five_Pillars_Presentation.aspx
Full episode on YouTube ▶️
https://youtu.be/UumRYf4WVsk
Beyond Coding Podcast with 🎙Patrick Akil
Powered by Xebia!!
OUTLINE
00:00:00 - Intro
00:00:26 - Dennis worked with JP (Xebia NL MD)
00:01:03 - Executive Briefing Center
00:01:43 - How Dennis ended up at Microsoft
00:04:01 - Joining a team focussed on Cloud Native Technology
00:06:22 - Creating win-wins
00:08:36 - Focus on adding value
00:11:02 - Gartner's Pace-Layered Application Strategy
00:14:15 - Low code and innovation
00:17:15 - Low code has a bad rep
00:18:21 - Patrick's experience with GenAI
00:19:52 - The value of Microsoft Copilot
00:22:16 - Common customer productivity challenges
00:25:07 - Exploring Platform Engineering
00:26:41 - Developer Productivity linked to Innovation
00:28:25 - Losing autonomy with Platform Engineering
00:30:01 - Focus on Tech, People and Process
00:31:28 - Sharing experiences on way of working
00:33:42 - Letting go of your ideas
00:34:30 - The role of an architect is evolving
00:36:38 - Jim Wilt and human dynamics
00:38:57 - When to push and pull
00:41:51 - The best ideas don't always win
00:44:09 - Include people along your journey
00:45:36 - Final thoughts
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 anywhereCloud native first principles: automate everything, tear down and rebuild clusters, and let only automation touch the clusterHome labs and offloading AI coding agents from your laptopPaved roads vs. golden cages: developer experience and agent experience with APIs and MCP serversBuilding platforms from the applications down, and fixing platform pain through pull requestsThis 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 - Intro00:00:45 - Why His Home Lab Now Runs 24/700:01:48 - Teaching Kubernetes: Students vs Skeptical Companies00:03:10 - Running AI Coding Agents in Sandboxes and Home Labs00:05:05 - The #1 Cloud Native Rule: Automate Everything00:07:30 - Tearing Down and Rebuilding Clusters Every Day00:09:10 - Why Kubernetes Rarely Broke for Him00:10:14 - How Much Kubernetes Should Software Engineers Know?00:12:53 - Why People Think Kubernetes Is Too Complex00:15:29 - How to Learn Kubernetes Without Getting Overwhelmed00:17:37 - Handling the Pressure of Infrastructure at Scale00:19:59 - When a Golden Path Becomes a Golden Cage00:25:43 - Designing Platforms for AI Agents With APIs and MCP00:27:54 - Build Platforms From Applications, Not the Tool Landscape00: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 Architecthttps://www.linkedin.com/in/thschue
#Kubernetes #PlatformEngineerin...
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 engineeringThe state a coding agent should be in before it runs for hours, and the gates its output has to passObservability with open-source MLflow when you can't read every traceA shared ontology and a three-layer memory stack: a Karpathy-style Markdown wiki in Obsidian, graph memory and a local vector database in DockerDisposable vs durable software, and why software built by intent threatens traditional SaaSWhy AI makes attacks cheaper than defenseThis 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 codeHow to stand out in interviews using the "Pumpkin" CV strategy, high-signal personal achievements, and human networkingWhy non-deterministic coding agents ignore skills.md files and why 88% of breaches come down to credentialsHow engineering leaders can implement deterministic runtime guardrails, workload identity, and scoped credentials at scaleWhether 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 Up00:00:47 - What a Field CTO Actually Does Every Day00:03:53 - Why 20% of Engineers Are Grieving Hands-On Coding00:06:55 - Why Hand-Crafted Code Is Becoming Like Carpentry00:08:26 - The Most Future-Proof Engineering Skill Nobody Wants00:10:53 - How to Network by Becoming the Connective Tissue00:13:55 - How to Stand Out When AI Writes Every Resume00:18:31 - The "Pumpkin" Strategy to Be Remembered in Interviews00:22:25 - Why Brilliant Engineers Avoid This Career Path00:26:42 - Why Skills Files Are Not Enough for Coding Agents00:31:10 - Building Determinist...
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 MetaHow top engineers treat on-call firefighting as a system-wide ownership opportunityWhy rotating between Engineering Manager (EM) and Staff IC sharpens your business and technical influenceTransitioning from Developer Experience (DX) to Agent Experience (AX) using MCP, Claude, and markdown contextThis 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 harnessesWhy AI skills files and “make no mistakes” prompts are only requests, and what replaces them in production pipelinesHow 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 SaaSFor 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 Has...
This podcast, its content and its artwork are not owned by, affiliated with, or endorsed by Castquire.