Picking up the thread from last week, Matt and Liam try to pin down what 'enterprise' actually means — and unpack why so much of the perceived cost of bespoke software is really the cost of enterprise overhead that most small businesses don't need.

Matt and Liam pick apart the persistent myth that custom software is only for big enterprises. From SMB access to risk, lock-in, and the manufacturing roots of enterprise software, they argue that bespoke isn't the dangerous option — homogenising your business to fit someone else's product is.

Matt and Liam unpack the EuroOffice scramble, the US CLOUD Act, and what data sovereignty actually means in 2026. It's a tour through Sun, Oracle, LibreOffice, the Microsoft Ireland case, and the uncomfortable questions every consultant should be asking about where their clients' data really lives.

Matt and Liam dig into Anthropic's unreleased Mythos model and the security implications everyone's talking about — then pull back the lens on AI hype cycles, data de-anonymisation, and whether we're sleepwalking through the biggest privacy breach in history.

Matt finally snaps. After a faulty GPU, a laptop that keeps rebooting itself, and a pre-installed audio driver that hides in System32 and reinstalls itself after every Windows Update, the only sensible move is nuclear — wipe the drive and switch to Linux. A deeply personal saga of hardware woes, vendor frustration, and one very stubborn rootkit.

Matt finally gets to debrief on .NET MAUI Day London — meeting the team in person, the talks that blew the room away, and why .NET 10 has him genuinely excited about mobile again. Plus: Liam's fully agentic AI game studio, and Matt's vibe-coded YouTube filter that may or may not be called the Fluff Slicer.

An AI agent submits a pull request, gets rejected, and publishes a hit piece. We unpack what happened, what it means for open source, and whether software engineers still have a job in 2026.

In this episode, Matt and Liam talk about hype cycles in modern tooling, using AI and Aspire as examples of what happens when tools are used outside their intended context. They explore why frustration often comes from misaligned expectations rather than broken technology.

A deeper follow-up to our earlier JavaScript discussions, this episode digs into why the ecosystem keeps tripping over the same problems. We unpack supply-chain risk, package culture, governance gaps, and the uncomfortable truth that some issues aren’t technical at all: they’re cultural. JavaScript isn’t going away, but that doesn’t mean it should remain the default foundation for everything we build.