
Sign up to save your podcasts
Or


In this episode, Matt and Liam unpack a feeling that’s been quietly building for a while: that many of the tools we’re excited about aren’t failing us: we’re failing to understand what they’re actually for.
What starts as a discussion about AI Foundry quickly turns into a broader reflection on hype cycles, developer expectations, and how easily we start bending our solutions to fit the tools, rather than the other way around.
This isn’t an anti-AI rant, and it’s not a “Microsoft bad” episode either. In fact, it’s almost the opposite. We talk about where these tools genuinely shine, why they do work for some people, and how frustration creeps in when we assume they’re meant for everyone and everything.
Along the way, we cover:
We also touch on resource hoarding, cloud ergonomics, managed identity pain, Cosmos DB emulators, container apps, and the uncomfortable reality that sometimes the problem isn’t the tool, it’s the assumptions we brought with us.
The takeaway isn’t “don’t use new things”. It’s slower, more annoying, and probably more useful than that:
Understand who a tool is for.
🍺 Liam - Homebrew
🥃 Matt - Aldi Scotch
Any Likes 👍, Shares 📣, Subscriptions 🔔, and Love ❤️ go a long way to helping us keep doing this for fun.
Cheers! 🍻
By Matt Goldman & Liam ElliottIn this episode, Matt and Liam unpack a feeling that’s been quietly building for a while: that many of the tools we’re excited about aren’t failing us: we’re failing to understand what they’re actually for.
What starts as a discussion about AI Foundry quickly turns into a broader reflection on hype cycles, developer expectations, and how easily we start bending our solutions to fit the tools, rather than the other way around.
This isn’t an anti-AI rant, and it’s not a “Microsoft bad” episode either. In fact, it’s almost the opposite. We talk about where these tools genuinely shine, why they do work for some people, and how frustration creeps in when we assume they’re meant for everyone and everything.
Along the way, we cover:
We also touch on resource hoarding, cloud ergonomics, managed identity pain, Cosmos DB emulators, container apps, and the uncomfortable reality that sometimes the problem isn’t the tool, it’s the assumptions we brought with us.
The takeaway isn’t “don’t use new things”. It’s slower, more annoying, and probably more useful than that:
Understand who a tool is for.
🍺 Liam - Homebrew
🥃 Matt - Aldi Scotch
Any Likes 👍, Shares 📣, Subscriptions 🔔, and Love ❤️ go a long way to helping us keep doing this for fun.
Cheers! 🍻