Hosted by Unknown Host · 🇺🇸 US · EN-US · 263 episodes
Established thought leaders with verified media credentials.
Working Code is a technology podcast unlike all others. Instead of diving deep into specific technologies to learn them better, or focusing on soft-skills, this one is like hanging out together at the water cooler or in the hallway at a technical conference. Working Code celebrates the triumphs and fails of working as a developer, and aims to make your career in coding more enjoyable.
Unknown Host hosts Working Code, a technology show with 263 episodes published.
It's a new year and you've probably got a mental list of things you want to learn. But how do you decide what's worth the investment? Ben explores the difference between "just-in-case" learning and "just-in-t
Tim stores his passwords in the browser. There, we said it. But before you grab your pitchforks, it turns out he's got an ancient password vault program backing him up—so he's not completely feral. Still, the hosts can't
Ben's been circling vibe coding for months, kept at bay by a simple fear: what if he spends more time fighting the AI over formatting than actually building anything? What if he has to bolt on linters and test runners ju
Adam built a Claude Code skill for his Taffy REST framework and wanted to share it with the CFML community. Simple enough—create a GitHub repo, add some markdown files, done. But somewhere between "this is cool"
How do you teach an LLM to write code you can actually trust? Carol's federal government team has been tasked with exploring unattended AI code generation, so she came to Adam and Tim for advice. Their first piece of gui
Ben had been riding high on vibe coding—throwaway scripts, zero attachment, pure productivity magic. Then he tried the same approach on a project he actually cares about and watched that 10x feeling crater to something c
For ten years, Adam's codebase has carried an ORM layer that everybody knew was wrong and nobody was touching. Nine hundred functions. Fifteen hundred files. The kind of job that gets solemnly nodded at in architecture m
Do commit messages even matter anymore, or did pull requests kill them? Ben works one commit per PR and thinks the commit message is the PR description. Carol and Tim put all the context in the PR and treat commits as di
Testing sounds simple until you actually try it. Private methods that can't be reached without hacks. Dependency injection that doubles your architecture's complexity before a single assertion runs. Production code that
Tim spent a single Sunday afternoon with Claude and built Show Bot -- a sarcastic Discord bot trained on every Working Code transcript, complete with a Dungeon Crawler Carl personality, fallacy detection badges, and a ta
What if the best way to get good work out of AI is to stop being nice to it? Adam and Tim have both landed on the same uncomfortable discovery: when you pit AI agents against each other, with fake points, opposing incent
The productivity gains are real. So is the nagging feeling that something else might be happening. The crew use AI every day, and this week they sit with a question they can't quite shake: when the tool handles more and
You spend all day steering AI through code. Then you step outside and it's steering everything else. AI is listening to therapy sessions and suggesting treatments to your therapist. Your spouse is arguing with a chatbot
It's 11:30 PM and you're still prompting. The code is better than anything you'd have shipped a year ago. The output is prolific, the roadmap is moving, the tooling is miraculous. So why are you still here at 11:30 PM? T
"We have solved all of the world's problems." Observability past the point where more logs stop helping, continuous deployment when the customer is the federal government and the change-management board is a real
Adam wrote a blog post this week about why AI keeps making him feel worse. This week is an honest conversation about the hypocrite's bind: needing to use the thing you recognize the harm of, and what that does to you. Fo
This week is a philosophical conversation about what you let into your head — the podcasts, the influencers, the political figures, the friends — and the difference between a snapshot you can hold at arm's length and a l
What's the point of a personal wiki when AI agents have already read the entire internet? This week is about patterns for co-maintaining a personal wiki with an AI agent, and where its job ends and yours begins. Follow t
Adam trained an AI on twenty years of Ben's blog, then asked Ben to pick his own words out of a lineup of forgeries. This week the hosts play a game of Ben or Bot, and you can play along too! Follow the show and be sure
It's the holidays, and the Working Code crew has a gift for you: a peek behind the velvet rope. In the spirit of Captain Crunch's "Oops! All Berries," this week's episode ditches the usual format entirely. No tri
Sponsor detection runs nightly. Check back soon.
No public pitch examples yet for this show.
Generate your own personalised pitchBased on semantic analysis of episode topics and host coverage, this show is a strong guest fit for executives in:
Industry fit is computed by PitchCentric using vector embeddings of the show's episode catalog.
Shows with the most semantically similar episode content. Pitch one, pitch all; producers cluster.
Working Code has a verified contact on file. Create a free PitchCentric account to access it and generate a personalised pitch in seconds. Research at least 3 recent episodes first and lead with a specific angle that serves their technology audience.
Working Code is hosted by Unknown Host. The show is categorised under technology and has published 263 episodes.
Working Code has published 263 episodes.
Working Code regularly covers technology. It sits in the technology category.
Working Code is accessible for guests with genuine technology expertise. A personalised, episode-aware pitch will still outperform a generic one every time.
Working Code hasn't explicitly signalled guest openness in recent episodes. That doesn't rule out pitching. your hook just needs to be especially compelling and relevant to their recent content.
Episodes of Working Code average 60 minutes. a focused format where a clear narrative arc and tight preparation matter most.
Our data rates Working Code's guest bar at 80/100 (Premium tier). Established thought leaders with verified media credentials. Sign in to PitchCentric to see how your own Pod Score compares against this show.
Methodology. Booking Probability™ blends Listen Score, 30-day Virality, open-to-guests detection, and Apple ratings. Data refreshed every 60 minutes. Listen Score and Booking Probability are calculated by PitchCentric. Last enriched 3 days ago.
