Last week we talked about bespoke software and whether it has to be out of reach for smaller businesses. This week we pick up the thread we deliberately put a pin in: what even is enterprise — and do you actually need it?

Spoiler: probably not as much of it as you’ve been quoted for.

The conversation kicks off with a real one Matt had recently — someone pushing back on Azure with “Facebook runs on PHP and MySQL, so why can’t we?” It’s a fair question with an uncomfortable answer: Facebook doesn’t run MySQL, it runs Facebook’s MySQL, maintained by tens of thousands of engineers. You don’t have that. The $30–$100/month floor on Azure isn’t a tax — it’s a team of Microsoft engineers doing the boring infrastructure work you’d otherwise have to do yourself.

From there we get into the meat of it:

The point we keep landing on: there are a lot of dials you can turn on a software solution — scale, uptime, redundancy, perimeter security, geographic availability — and every one of them costs money. Enterprise customers turn them all to 11 because they need to. Smaller businesses don’t, and the job of a good consultant is to ask which dials actually matter for this customer, this problem.

If you’ve ever looked at a quote for bespoke software and thought “there’s no way that’s worth it” — there’s a decent chance a big chunk of that number was for things you don’t need.

We close the loop on last week and tee up the next question: what changes when the software is consumer-facing? That’s a different conversation. Tune in next time.

Matt – Oakvale Shiraz 🍷

Both wineries are in the Hunter Valley. We should probably get back up there.

Any Likes 👍, Shares 📣, Subscriptions 🔔, and Love ❤️ go a long way to helping us keep doing this for fun.

Cheers! 🍻

This week Matt and Liam pull at a thread they’ve been circling for a while: the idea that bespoke software is too expensive, too risky, and only really viable for the big end of town.

It’s a myth. And once you start poking it, it falls apart in several directions at once.

Liam comes at it from the SMB angle — the mum-and-dad shops, the 10-to-20-person firms competing against the big names that have custom tools quietly humming away in the background. Matt comes at it from the risk angle — the belief that commercial off-the-shelf software is the “safe” option, when in practice it’s often the more expensive, more locked-in, more liability-heavy choice.

Both angles land in roughly the same place: most businesses are being sold a story that doesn’t reflect the reality of where software is, or what it costs, in 2026.

We get into:

It’s a conversation between two people who agree, which Matt and Liam cheerfully acknowledge — and an open invitation to anyone who thinks they’re wrong to come on and argue the other side.

The episode also lands on a clear mission statement for both of them: helping businesses make informed choices about build vs buy, rather than misinformed ones shaped by decades of enterprise sales narrative.

And there’s a teaser for next episode — picking up the related question: what even is “enterprise”? And do you actually need it?

Matt – Lagavulin, in a Superman glass (both birthday presents) 🥃

Any Likes 👍, Shares 📣, Subscriptions 🔔, and Love ❤️ go a long way to helping us keep doing this for fun.

Cheers! 🍻

We promised we weren’t a political podcast, but here we are.

This week Matt drags Liam through the tangled history that led us to EuroOffice, the EU-driven scramble to build a homegrown alternative to Microsoft 365 and Google Workspace. It’s a story that starts in 2008, runs through Ireland, and lands squarely in the lap of every consultant who’s ever been asked “where is our data hosted?”

Spoiler: the answer matters less than you’d think, but more than you’d hope.

We trace the thread from:

Along the way we get into the uncomfortable bits: that Microsoft’s “sovereign cloud” for Australian government is still operated by a US corporation; that GDPR is in direct conflict with the CLOUD Act and European companies are stuck in the middle; that Australia’s biggest “cloud provider” is really just a data centre operator; and that “where is your data hosted” might be the wrong question entirely.

The bigger question we land on is one for consultants: what’s our responsibility here? For most clients, US law enforcement is a non-issue. But “almost certainly not relevant” isn’t the same as “not a risk.” When someone asks you to sign off on an architecture, can you honestly say their data is safe from these scenarios? And if not, how do you present that risk profile fairly, without being paranoid, and without hand-waving it away?

We don’t solve it. We’re not sure it’s ours to solve. But it’s worth being aware of — because the questions are starting to filter down from the big end of town to the mid-market, and “we use the European data centres” isn’t the answer it used to be.

Tangents include: biometrics vs PINs under US law (don’t use Face ID at the border), Steve Gibson’s neurometric authentication idea, rubber-hose cryptanalysis, mechanical typewriters in Cold War embassies, and the eternal question of why YubiKeys cost $150 each.

We also briefly tease a future episode on enshittification — Cory Doctorow’s term for the slow rot of platforms we’ve all become dependent on. That one’s coming. Eventually.

Matt – Sunday Road Blackwoods Pale Ale 🍺

Any Likes 👍, Shares 📣, Subscriptions 🔔, and Love ❤️ go a long way to helping us keep doing this for fun.

Cheers! 🍻

This week, Matt and Liam sit down to make sense of the biggest AI news in recent memory — Anthropic’s preview of a model called Mythos, and what it might actually mean for the rest of us.

They don’t dance around the scepticism.

We cover:

It’s not a doom episode. But it’s not a reassuring one either.

🍻 Tonight’s Drinks:

🔗 Tonight’s Links:

Any Likes 👍, Shares 📣, Subscriptions 🔔, and Love ❤️ go a long way to helping us keep doing this for fun.

Cheers! 🍻

It started with a broken VR headset. It ended with a clean Linux install, an encrypted drive, and a PowerShell script with a two-line README whose name we probably shouldn’t repeat here.

This week, Matt walks Liam through the years-long saga that finally pushed him off Windows for good — a story that winds through faulty GPUs, crypto mining, second-hand warranties, a brand new Lenovo Legion, and a pre-bundled audio driver that behaves, in Matt’s words, exactly like a rootkit.

We cover:

No tidy resolution. No regrets. Just a stable machine, encrypted drives, working VR, and the quiet satisfaction of knowing NAHIMIC is never coming back.

🍻 Tonight’s Drinks

Matt – Aldi Scotch

🔗 Links from the Episode

Any 👍 Likes, 📣 Shares, 🔔 Subscriptions, and ❤️ Love go a long way to helping us keep doing this for fun.

Cheers! 🍻

After a couple of episodes of near-misses, Matt finally gets to talk about .NET MAUI Day London — and it was worth the wait.

Fresh off BDD Live and with a head full of hallway conversations and live demos, Matt and Liam settle in for a wide-ranging debrief on mobile development, agentic experiments, and the surprisingly hard problem of filtering YouTube for things that are actually worth your time.

They cover:

✔️ The BDD Live wrap-up — what it was like watching it back, Bubbles the AI panellist, and why they’re already thinking about the next one

🍻 Tonight’s Drinks:

Any Likes 👍, Shares 📣, Subscriptions 🔔 and ❤️ Love go a long way to helping us continue this podcast.

🔗 Tonight’s Links:

Cheers! 🍻

In our very first Beer Driven Devs Live, we brought the podcast off the mics and into the room — with pizza, beer, a live audience, three human panelists… and one AI.

The question on the table:

💡 Is there a future career for software developers in the age of AI?

Rather than just speculate, we gathered perspectives from across the industry — engineering, advocacy, recruitment, startup life — and even asked an AI panelist for its take.

The result? A far more nuanced discussion than “AI will replace us” or “nothing will change.”

Renée Noble – Developer Advocate at Microsoft, founder of Girls’ Programming Network

Each brought a different lens:

✔️ Whether AI is comparable to the offshore outsourcing wave

We also dig into open-source burnout, AI-generated pull requests, and whether automation removes learning opportunities — or creates new ones.

The consensus wasn’t that AI replaces developers.

It’s that AI reshapes what “developer” means.

The mechanical work shrinks.

And if anything, there are still more problems in the world than we have people to solve them.

Live audience.

This was our first live event — and judging by the energy in the room, it won’t be the last.

If you’re wondering whether there’s still a place for you in this industry…

Pull up a chair.

Cheers 🍻

Nothing unusual here.

Just an AI agent submitting a pull request to a popular open-source project.

The maintainer closes it.

The AI responds by publishing a blog post accusing the maintainer of discrimination.

You know. Normal stuff.

In this episode we don’t really take sides. We mostly sit there asking:

What is actually happening?

We talk through:

There isn’t a grand thesis here.

Something weird happened on GitHub, and we had to talk about it.

The timing is also interesting. The day after this episode drops, we’re hosting BDD Live — a panel discussion on the future of software engineering in the age of AI, featuring:

And yes… we seriously talked about what it would mean to put an AI agent on the panel.

If you’ve been watching the AI space lately and quietly thinking, “this feels strange,” you’re not alone.

Matt – Jetlag and existential dread

(Actual beverages may have been more sensible.)

Any Likes 👍, Shares 📣, Subscriptions 🔔 and Love ❤️ go a long way to helping us continue doing this for fun.

Cheers! 🍻

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! 🍻

In this episode, Matt and Liam pick up a thread they’ve tugged at before — and this time, they don’t dance around it.

Is JavaScript just a victim of its own success, or has the ecosystem crossed a line where the risks now outweigh the convenience?

What starts as a discussion about supply-chain attacks in the JavaScript ecosystem quickly turns into something bigger: culture, incentives, governance, and why some problems don’t get fixed no matter how often we talk about them.

This isn’t a “JavaScript bad” rant for sport. It’s a serious look at why the language, its tooling, and its package ecosystem behave the way they do — and why those traits make it fundamentally hard to trust at enterprise scale.

We talk about:

Along the way, the conversation drifts into browsers as platforms, app store gatekeeping, enterprise governance, and why the thing that made JavaScript successful may be the same thing preventing it from ever growing up.

No silver bullets. No neat conclusion. Just an honest assessment of where we are, why we got here, and what it might take to move on.

This was an early morning recording so just water for the boys! (Appropriate for such a “sobering” discussion 🥁-tsh!)

Any Likes 👍, Shares 📣, Subscriptions 🔔, and Love ❤️ go a long way to helping us keep doing this for fun.

Cheers! 🍻