CaSE Podcast Team
59 episodes listed below
PRESS PLAY
Conversations about Software Engineering (CaSE) is a podcast for software engineers about technology, software engineering, software architecture, reliability engineering, and data engineering. The three of us regularly come together to discuss recent events or articles, exchange on our learnings, and reflect on our professional and personal experiences. Additionally our guest episodes feature engaging conversations with interesting people from the world of software engineering.
Based on 6 episodes we listened to · September 2026
CaSE turns architecture, infrastructure, and AI tooling into candid conversations about engineering judgment and its consequences.
CaSE: Conversations about Software Engineering follows technical ideas into the decisions that make them useful. The hosts give guests room to connect engineering history with current practice, moving from DTrace and eBPF to observability products, cloud-native testing, data…
A steak detour before DTrace: your kind of engineering chat if curiosity takes the scenic route.
Press play if you want
Short reviews from the PlayNext desk, based on the episodes we processed.
A practical talk about sensitivity points, architecture, and AI assistance.
The episode treats architecture as a risk problem, not just a diagramming exercise. It opens with sensitivity points and a Volkswagen data breach example, then stays focused on how software teams should think when a small change can create a large failure.
Harness engineering makes agent talk feel like a real software design problem.
Birgitta Bockeler's return to CASE reads less like a grand theory piece and more like a useful look at how AI-assisted software delivery actually gets built.
A grounded look at ADRs, architectural debt, and the trust built by documenting hard decisions.
Andrew keeps the focus on the practical side of architecture decisions: making them visible, writing down the trade-offs, and leaving a way to revisit them later. The point is not theory for its own sake.
A measured relaunch that resets the hosts and restores the show's software-engineering focus.
CASE Reloaded comes back as a plain relaunch. Sven introduces the return after a long break, names the new hosts Heinrich and Alex, and restates the show's focus on software engineering and open-ended technical talk.
A practical case for treating data like a product, not a pile of hope.
Simon Harrer and the hosts keep the episode focused on a simple question: what does it take to ship a data product another team can actually use? The strongest stretches stay close to interfaces, customers, and the gap between owning data and serving it.
A grounded guide to keeping hard technical meetings from turning sharper than they need to be.
Aino Cori comes across as a seasoned independent consultant, and that background gives the conversation a useful range. It starts with retrospective anti-patterns, then keeps widening the lens to technical meetings, architecture reviews, and the everyday friction that shows up…
Specialists walking through software's tradeoffs, one system at a time.
Founders and engineers on AI coding agents like Claude Code, and supply chain security.
The engineering decisions behind code, agents, and control.
Python tools, practical trade-offs, and the occasional programming joke.
Matt Stratton interviews DevOps practitioners on security, platform engineering, and trusting AI-written code.
Andrew joins a conversation about making architecture decisions clearer and easier to revisit.
Ole Lensmar, a veteran testing tool builder, admits he's not a fan of the 99% code coverage philosophy.
Aino joins Sven for a long talk about tense meetings.
Birgitta Bockeler returns to CASE for a conversation with Sven and Heinrich about AI-assisted software delivery and the newer term around harness engineering.
Simon Harrer joins the CASE Podcast.
CASE Reloaded marks the podcast's return after about a year and a half without a recording.
Sven, Alex, and Heinrich start with a loose end-of-week check-in, then turn to architectural thinking around sensitivity points.
Heinrich discusses practical approaches to software architecture governance, framing it as a tool to enable team autonomy rather than impose rigid rules.
Angelo Veltens of CodeCentric, who works on Solid OS with Tim Berners-Lee's Solid community, says siloed apps like Signal, WhatsApp, Google Calendar and Microsoft Teams leave users without control over their data.