Working Code

Tim is trying to hire remote developers, but the interviews have started to feel like one long CAPTCHA. Before he can decide who's right for the job, he has to figure out whether he's interviewing the candidate or ChatGPT. This week the hosts discuss the state of remote developer interviews in the AI era.Follow the show and be sure to join the discussion on Discord! Our website is workingcode.dev and we're @workingcode.dev on Bluesky. New episodes drop weekly on Thursday.And, if you're feeling the love, support us on Patreon.Mentioned in this episode:Mostly Technical #29: “Super Epic Crazy” — the source of the cover-letter story about most applicants missing simple instructionsRoberto Serrano on AI fraud at Brown University — the course whose take-home exams triggered the in-class-final storyWith audio editing and engineering by ZCross Media.Full show notes and transcript here.

They say history doesn't repeat itself, it rhymes, and apparently so do show topics. A year on from our episode on the value of friction, the crew are back to discuss value of struggle. The question this time: now that AI will cheerfully do the hard part for you, which struggles are worth keeping, and which you can finally hand off?Follow the show and be sure to join the discussion on Discord! Our website is workingcode.dev and we're @workingcode.dev on Bluesky. New episodes drop weekly on Thursday.And, if you're feeling the love, support us on Patreon.Mentioned in this episode:Ronny Chieng's Harvard Class Day speech — the "your generation's job is to kill AI" address.With audio editing and engineering by ZCross Media.Full show notes and transcript here.

Eighteen weeks ago Adam handed his decade-old ORM layer to an AI agent. This week he kills the whole refactor — and the feeling that comes isn't regret, it's relief. Somewhere in the grind he realized he'd only ever weighed two options, push through or admit defeat, and both assumed he had to see it to the end. This week is about sunk cost — how being partway down a road can convince you that you owe it the rest of the way, and how freeing it is to decide you don't.Follow the show and be sure to join the discussion on Discord! Our website is workingcode.dev and we're @workingcode.dev on Bluesky. New episodes drop weekly on Thursday.And, if you're feeling the love, support us on Patreon.Mentioned in this episode:249: 10 Years of Tech Debt — where Adam first handed the ORM layer to an agentWith audio editing and engineering by ZCross Media.Full show notes and transcript here.

The promise was that AI would take the grunt work off your plate and leave you the good stuff. This week is the part no one advertised: you got into this to make things — but what comes instead is the restless guilt of sitting there with nothing to do while the agent works, and the slow realization that when it finishes, the job left for you is mostly reviewing.Follow the show and be sure to join the discussion on Discord! Our website is workingcode.dev and we're @workingcode.dev on Bluesky. New episodes drop weekly on Thursday.And, if you're feeling the love, support us on Patreon.Mentioned in this episode:xkcd: "Compiling"With audio editing and engineering by ZCross Media.Full show notes and transcript here.

Getting unstuck has gotten so cheap that Ben can't remember the last time he actually learned something at work — and the struggle he's skipping was where knowing the code, and caring about it, used to come from. This week is a conversation about what software craftsmanship even means anymore, when the tools are happy to do the caring for you.Follow the show and be sure to join the discussion on Discord! Our website is workingcode.dev and we're @workingcode.dev on Bluesky. New episodes drop weekly on Thursday.And, if you're feeling the love, support us on Patreon.With audio editing and engineering by ZCross Media.Full show notes and transcript here.

This week is the quiet worry underneath all the productivity gains: that every time you hand the boring work to a machine, you're handing over a little of the curiosity that made you good at the work you care about, until one day the well of ideas just runs dry.Follow the show and be sure to join the discussion on Discord! Our website is workingcode.dev and we're @workingcode.dev on Bluesky. New episodes drop weekly on Thursday.And, if you're feeling the love, support us on Patreon.Mentioned in this episode:Taffy — the REST framework for ColdFusion and LuceeRest Assured by Adam TuttlePostmanEngineering ExplainedWith audio editing and engineering by ZCross Media.Full show notes and transcript here.

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 to join the discussion on Discord! Our website is workingcode.dev and we're @workingcode.dev on Bluesky. New episodes drop weekly on Thursday.And, if you're feeling the love, support us on Patreon.Mentioned in this episode:Play "Ben's Blog or AI?" yourselfThe Pragmatic Programmer: From Journeyman to MasterDomain-Driven Design by Eric EvansMassTransitWith audio editing and engineering by ZCross Media.Full show notes and transcript here.

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 the show and be sure to join the discussion on Discord! Our website is workingcode.dev and we're @workingcode.dev on Bluesky. New episodes drop weekly on Thursday.And, if you're feeling the love, support us on Patreon.Mentioned in this episode:Karpathy's LLM Wiki gistWith audio editing and engineering by ZCross Media.Full show notes and transcript here.

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 living relationship you're quietly being shaped by.Follow the show and be sure to join the discussion on Discord! Our website is workingcode.dev and we're @workingcode.dev on Bluesky. New episodes drop weekly on Thursday.And, if you're feeling the love, support us on Patreon.Mentioned in this episode:Fritz Haber (YouTube)With audio editing and engineering by ZCross Media.Full show notes and transcript here.

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.Follow the show and be sure to join the discussion on Discord! Our website is workingcode.dev and we're @workingcode.dev on Bluesky. New episodes drop weekly on Thursday.And, if you're feeling the love, support us on Patreon.Mentioned in this episode:Adam's blog post: "On the AI of It All"Impeccable StyleMental NotesWith audio editing and engineering by ZCross Media.Full show notes and transcript here.

"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 room with real people in it, JSON's loose schema as a load-bearing feature rather than a quirk to apologise for, and the awkward question of who actually owns the code you wrote on a work-issued machine.Follow the show and be sure to join the discussion on Discord! Our website is workingcode.dev and we're @workingcode.dev on Bluesky. New episodes drop weekly on Thursday.And, if you're feeling the love, support us on Patreon.With audio editing and engineering by ZCross Media.Full show notes and transcript here.

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? This week is an honest conversation about the strange shape of burnout in the AI era — the productivity that keeps compounding, the bar that keeps rising right along with it, and the quiet feeling that somewhere in the last year the craft stopped feeling quite like yours.Follow the show and be sure to join the discussion on Discord! Our website is workingcode.dev and we're @workingcode.dev on Bluesky. New episodes drop weekly on Thursday.And, if you're feeling the love, support us on Patreon.With audio editing and engineering by ZCross Media.Full show notes and transcript here.

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 about where Savannah, Georgia is. You call a company for help and get handed from one AI pretending to be human to another AI pretending to be human. The crew has been noticing it everywhere, and this week they compare notes on what it actually feels like when AI stops being a tool you chose and starts being a thing that just happens to you.Links mentioned in the show:hairstyles.netRunPee.comFollow the show and be sure to join the discussion on Discord! Our website is workingcode.dev and we're @workingcode.dev on Bluesky. New episodes drop weekly on Thursday.And, if you're feeling the love, support us on Patreon.With audio editing and engineering by ZCross Media.Full show notes and transcript here.

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 more of the thinking, what does that do to the person using it?Follow the show and be sure to join the discussion on Discord! Our website is workingcode.dev and we're @workingcode.dev on Bluesky. New episodes drop weekly on Thursday.And, if you're feeling the love, support us on Patreon.With audio editing and engineering by ZCross Media.Full show notes and transcript here.

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 incentives, and competing models, the output gets dramatically better than anything a single polite prompt can produce.Adam's bug-hunting pipeline hands fake rewards to sycophantic agents and then throws the scores in the trash. Tim made Claude and ChatGPT argue for twelve rounds straight until they both said "ship it".Follow the show and be sure to join the discussion on Discord! Our website is workingcode.dev and we're @workingcode.dev on Bluesky. New episodes drop weekly on Thursday.And, if you're feeling the love, support us on Patreon.With audio editing and engineering by ZCross Media.Full show notes and transcript here.

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 talent for roasting anyone who tries to prompt-inject it. The conversation turns into a deep technical walkthrough of RAG pipelines, local models, cross-encoder reranking, and what happens when you just start building things that make you laugh.Follow the show and be sure to join the discussion on Discord! Our website is workingcode.dev and we're @workingcode.dev on Bluesky. New episodes drop weekly on Thursday.And, if you're feeling the love, support us on Patreon.With audio editing and engineering by ZCross Media.Full show notes and transcript here.

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 slowly warps around your test suite instead of the other way around. Ben has spent his entire career shipping code without tests, and this week he decided to change that. The crew walks him through every trap he steps on, and a few they've been stuck in themselves.LinksBen Nadel's BlogFollow the show and be sure to join the discussion on Discord! Our website is workingcode.dev and we're @workingcode.dev on Bluesky. New episodes drop weekly on Thursday.And, if you're feeling the love, support us on Patreon.With audio editing and engineering by ZCross Media.Full show notes and transcript here.

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 disposable breadcrumbs. Adam's somewhere in between — when he's not pushing thirty knife emojis and "nope, still not working" to QA. Meanwhile, Tim's back from emergency eye surgery with a gas bubble floating around his eyeball.LinksBen Nadel's BlogConventional CommitsFollow the show and be sure to join the discussion on Discord! Our website is workingcode.dev and we're @workingcode.dev on Bluesky. New episodes drop weekly on Thursday.And, if you're feeling the love, support us on Patreon.With audio editing and engineering by ZCross Media.Full show notes and transcript here.

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 meetings and quietly dies on the roadmap — every single year. So he stopped waiting for a volunteer and handed it to an AI agent instead. Claude's problem now.Follow the show and be sure to join the discussion on Discord! Our website is workingcode.dev and we're @workingcode.dev on Bluesky. New episodes drop weekly on Thursday.And, if you're feeling the love, support us on Patreon.With audio editing and engineering by ZCross Media.Full show notes and transcript here.

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 closer to 10%. The bottleneck, it turns out, was never the typing.The hosts dig into what it feels like to let go of code you used to care about, whether "write-only code" is actually the future, and the growing gap between building software and keeping it alive.LinksVibe Coding by Gene Kim & Steve Yegge - The audiobook on AI-assisted development1Password: From Magic to Malware - How OpenClaw's agent skills became a supply chain attack surfaceTLDR Newsletter - Source of the "write-only code" conceptFollow the show and be sure to join the discussion on Discord! Our website is workingcode.dev and we're @workingcode.dev on Bluesky. New episodes drop weekly on Thursday.And, if you're feeling the love, support us on Patreon.With audio editing and engineering by ZCross Media.Full show notes and transcript here.

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" and "anyone can install this," a familiar chill crept in. These skills are just text files. No checksums. No digital signatures. No verification that the thing you're installing won't quietly exfiltrate your code to some server in Eastern Europe. Sound familiar? It should. We've been here before—back when passwords lived in plain text and "security" meant hoping nobody looked too hard.The hosts dig into the unsettling parallels between today's LLM plugin ecosystem and the wild west of early internet security.LinksAdam's Dotfiles Blog Post - Getting his shit together with dotfiles, Brewfile, and 1Password SSH agentCF Community LLM Marketplace - Adam's community marketplace for CFML-related Claude skillsSteve Yegge's Google Platforms Rant - The infamous accidentally-public Google+ postVibe Coding by Gene Kim & Steve Yegge - The audiobook Ben's been enjoyingSocket.dev - Supply chain security for npm dependenciesFollow the show and be sure to join the discussion on Discord! Our website is workingcode.dev and we're @workingcode.dev on Bluesky. New episodes drop weekly on Thursday.And, if you're feeling the love, support us on Patreon.With audio editing and engineering by ZCross Media.Full show notes and transcript here.

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 just to babysit the output? Then his work handed him a Claude plan, and he decided it was finally time to take the plunge. And then something unsettling happened—the code looked like his code. Same line lengths. Same method ordering. Same obsessive formatting. Nobody told it to do that. It just... knew.Meanwhile, Adam has gone full mad scientist. His "Ralph" workflow runs Claude in a loop, feeding it tasks from a JSON file while he walks away to eat dinner. When he comes back, features are done. Tests pass. The machine just keeps building. It's the kind of setup that makes you wonder why you're still manually typing commands into a terminal.LinksAdam's Ralph Workflow for Claude Code - Adam's blog post with his implementationMatt Pocock's Ralph Primer Video - The workflow Adam adapted for automated iterative developmentAlgorithm Maze Race - Tim's vibe-coded game on itch.ioPro tip: Use /resume in Claude Code to return to prior sessionsFollow the show and be sure to join the discussion on Discord! Our website is workingcode.dev and we're @workingcode.dev on Bluesky. New episodes drop weekly on Thursday.And, if you're feeling the love, support us on Patreon.With audio editing and engineering by ZCross Media.Full show notes and transcript here.

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 resist a good-natured intervention. What starts as a gentle roasting turns into a deep dive on password managers, shared family vaults, and why your retirement account deserves better than Chrome's autofill. Carol reveals her galaxy-brain solution to her husband constantly forgetting his master password: she just signed him into her account. He still doesn't know he doesn't have his own 1Password.LinksClaude Code - Anthropic's CLI for coding with ClaudeRalph Wiggum Plugin - Official Claude Code plugin for autonomous loopsEverything is a Ralph Loop - Geoffrey Huntley's deep dive on the techniqueFollow the show and be sure to join the discussion on Discord! Our website is workingcode.dev and we're @workingcode.dev on Bluesky. New episodes drop weekly on Thursday.And, if you're feeling the love, support us on Patreon.With audio editing and engineering by ZCross Media.Full show notes and transcript here.

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-time" learning, while grappling with AI anxiety and the fear of falling behind. Along the way, Tim shares his own struggle—turns out, saying goodbye to something you built hits different.Follow the show and be sure to join the discussion on Discord! Our website is workingcode.dev and we're @workingcode.dev on Bluesky. New episodes drop weekly on Thursday.And, if you're feeling the love, support us on Patreon.With audio editing and engineering by ZCross Media.Full show notes and transcript here.

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 triumphs, no fails, no structured topic—just pure, unfiltered aftershow energy.Tim unpacks Cory Doctorow's concept of "reverse centaurs"—what happens when you're not assisted by AI, but reduced to its peripheral? Meanwhile, Adam drops a perspective on humanity's place in the universe that reframes everything you thought you knew about time. That, plus Carol humbling an AI chatbot, the death of the golden age of television, and whether the books you loved as a kid were actually any good.Follow the show and be sure to join the discussion on Discord! Our website is workingcode.dev and we're @workingcode.dev on Bluesky. New episodes drop weekly on Wednesday.And, if you're feeling the love, support us on Patreon.With audio editing and engineering by ZCross Media.Full show notes and transcript here.

It's that time of year—each host reaches into Santa's sack of topics to see who's been naughty and who's been nice. Ben returns from visiting his employer's manufacturing headquarters in Georgia with some philosophical musings. Carol is on a mission to slash CI/CD build times. Adam has cautiously optimistic news about passkeys finally working (sometimes). And Tim reflects on a TLDR article suggesting that the management skills you've built—knowing what to build and what not to build—might be exactly what AI-era coding demands.Plus: December blues, mushroom tea for focus, and jQuery as peak imperative JavaScript.Links mentioned:Owning A Lucid Has Been Super DisappointingDriving Xiaomi's Electric Car: Are we Cooked?Follow the show and be sure to join the discussion on Discord! Our website is workingcode.dev and we're @workingcode.dev on Bluesky. New episodes drop weekly on Wednesday.And, if you're feeling the love, support us on Patreon.With audio editing and engineering by ZCross Media.Full show notes and transcript here.

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 guidance: whatever tools you pick today will be obsolete by the time you're done evaluating them. The real goal isn't adopting a specific workflow—it's building the skills to ride the wave.Follow the show and be sure to join the discussion on Discord! Our website is workingcode.dev and we're @workingcode.dev on Bluesky. New episodes drop weekly on Wednesday.And, if you're feeling the love, support us on Patreon.With audio editing and engineering by ZCross Media.Full show notes and transcript here.

Remember that you will die. That's the meaning behind "Memento Mori," and it's the theme of this week's episode. Guest Shawn Oden, joins Adam, Ben, and Tim to discuss digital death preparedness for geeks. Inspired by clearing out his grandmother's house and buying his late best friend's computers to protect his digital legacy (and potentially lost Bitcoin), Shawn advocates for documenting passwords, creating wills, setting up power of attorney, and having honest conversations with loved ones. The hosts explore practical steps like using 1Password with shared family vaults, the importance of organ donation documentation, and the philosophical tension between honoring a deceased person's wishes versus meeting the needs of those left behind.Follow the show and be sure to join the discussion on Discord! Our website is workingcode.dev and we're @workingcode.dev on Bluesky. New episodes drop weekly on Wednesday.And, if you're feeling the love, support us on Patreon.With audio editing and engineering by ZCross Media.Links & ResourcesIn Case You Get Hit by a Bus (book)eol-dr - End of Life Digital Resources on GitHubEOL-RalphHightower - Another digital estate planning resourceNOLO - Get Your Affairs in Order - Legal self-help resourcesFull show notes and transcript here.

How do you stay motivated when you're stuck building features you don't understand? Carol brings a conversation she's been having with her team about feeling like a "feature factory"—churning out work without clarity on what problem they're solving or what value it adds. When every standup is "is this done?" instead of "have we made anything better?", burnout follows fast. The hosts explore the tension between customer-driven features, competitive pressure, arbitrary boss decisions, and the human need to feel connected to meaningful work.Follow the show and be sure to join the discussion on Discord! Our website is workingcode.dev and we're @workingcode.dev on Bluesky. New episodes drop weekly on Wednesday.And, if you're feeling the love, support us on Patreon.With audio editing and engineering by ZCross Media.Full show notes and transcript here.

What happens when your passion project becomes so successful that you have to shut it down? Advent of Code creator Eric Wastl announced he was scaling back from 25 days to 12 and removing the global leaderboard. The reason? People were feeling bad at their jobs because they couldn't solve puzzles in 45 seconds like the leaderboard speedrunners.Quiet UI launched with excitement, garnered incredible buzz, and shut down three weeks later when the demands became overwhelming.This week, the hosts explore how good intentions collide with bad behavior—where success becomes punishment, communities ruin what was made for them, and the people who just wanted to share something cool are forced to walk away.Follow the show and be sure to join the discussion on Discord! Our website is workingcode.dev and we're @workingcode.dev on Bluesky. New episodes drop weekly on Wednesday.And, if you're feeling the love, support us on Patreon.With audio editing and engineering by ZCross Media.Full show notes and transcript here.

When you use ChatGPT instead of Google, you're not just getting a faster answer—you're cutting out the content creators who made that knowledge possible. In this week's episode, we explore the economics of AI search, the death of Stack Overflow, the junior developer problem writ large, and why capitalism keeps pushing moral responsibility onto individuals who have the least power to change anything.Follow the show and be sure to join the discussion on Discord! Our website is workingcode.dev and we're @workingcode.dev on Bluesky. New episodes drop weekly on Wednesday.And, if you're feeling the love, support us on Patreon.With audio editing and engineering by ZCross Media.Full show notes and transcript here.

In this week's episode the gather round and share what they've been up to for trunk or treat. Adam shares his waning motivation for his Jump Run side project, we explore sustainable motivation, the rewrite temptation, and whether it's okay to just... do the fun thing sometimes. Meanwhile, Tim provides a reality check on AI coding tools—he spent real hours comparing GitHub Copilot and Codex on actual work, and the results are messier than the hype suggests.Follow the show and be sure to join the discussion on Discord! Our website is workingcode.dev and we're @workingcode.dev on Bluesky. New episodes drop weekly on Wednesday.And, if you're feeling the love, support us on Patreon.With audio editing and engineering by ZCross Media.Full show notes and transcript here.

How do you keep millions of people safe on 40 different dating sites while simultaneously figuring out what drives them to buy memberships? Sean Corfield joins Adam and Ben to discuss the surprisingly complex engineering and business challenges of observing user behavior at massive scale.Sean runs us through fraud detection and prevention (including devastating "pig butchering" romance scams), database architecture at enormous scale (700GB databases with 250M+ row tables), custom domain-specific languages for writing business rules without touching SQL, real-time scoring systems with hundreds of rules, zero-downtime deployments and schema migrations, and the constant cat-and-mouse game between scammers and detection systems.Follow the show and be sure to join the discussion on Discord! Our website is workingcode.dev and we're @workingcode.dev on Bluesky. New episodes drop weekly on Wednesday.And, if you're feeling the love, support us on Patreon.With audio editing and engineering by ZCross Media.Full show notes and transcript here.

Can you really multitask, or are you just rapidly switching between contexts and hoping your brain doesn't lose track? This week, we dig into the cognitive load of deep work, the impossibility of maintaining multiple large projects in your head simultaneously, and the ADHD patterns that shape how many of us think and work.Carol returns from the chaos of federal government planning meetings with renewed energy and alignment. Adam finds flow in his Jump Run project while navigating compliance season. Ben discovers the exhausting reality of writing actual specification documents for the first time in his career—and realizes just how taxing deep thinking can be.reCAPTCHA Migration: https://privatecaptcha.com/blog/recaptcha-migration-to-google-cloud-2025/Follow the show and be sure to join the discussion on Discord! Our website is workingcode.dev and we're @workingcode.dev on Bluesky. New episodes drop weekly on Wednesday.And, if you're feeling the love, support us on Patreon.With audio editing and engineering by ZCross Media.Full show notes and transcript here.

How do you resist the siren call of shiny new features when you're months into a project that really matters?Adam finds himself six weeks into a 12-week build when his boss floats a couple of juicy AI integration ideas. Ben relates this to his own tendency to get distracted by massive refactors mid-feature. They dig into strategies for staying disciplined—like using future work as motivation, finding small wins along the way, or accepting that sometimes work just has to feel like work..Follow the show and be sure to join the discussion on Discord! Our website is workingcode.dev and we're @workingcode.dev on Bluesky. New episodes drop weekly on Wednesday.And, if you're feeling the love, support us on Patreon.With audio editing and engineering by ZCross Media.Full show notes and transcript here.

In this week's episode the crew is back to discuss the never-ending journey of self-improvement in the tech industry, are we idiots to ignore it or maniacs to go along with it? Ben and Tim are back from CF Summit to recount there experiences where a big topic of discussion was... you guessed it, AI.Follow the show and be sure to join the discussion on Discord! Our website is workingcode.dev and we're @workingcode.dev on Bluesky. New episodes drop weekly on Wednesday.And, if you're feeling the love, support us on Patreon.With audio editing and engineering by ZCross Media.Full show notes and transcript here.

In this week's episode the whole crew is back, and Ben brings our attention to "good" friction. It's all too common in business to hear about reducing and eliminating friction, but some forms of friction can be positive in ways we take for granted.Follow the show and be sure to join the discussion on Discord! Our website is workingcode.dev and we're @workingcode.dev on Bluesky. New episodes drop weekly on Wednesday.And, if you're feeling the love, support us on Patreon.With audio editing and engineering by ZCross Media.Full show notes and transcript here.

Common sense isn't so common, or maybe it's a myth entirely? On this week's episode, Adam, Ben, and Carol discuss common sense in programming.What may be common sense to a programmer may not be so simple to a user, and it's important, in these contexts, to deploy empathy and understanding rather than frustration. The hosts discuss this and more.A Hermeneutic of Generosity https://www.youtube.com/watch?v=ovrzKCQ2JTMTen Thousand https://xkcd.com/1053/Follow the show and be sure to join the discussion on Discord! Our website is workingcode.dev and we're @workingcode.dev on Bluesky. New episodes drop weekly on Wednesday.And, if you're feeling the love, support us on Patreon.With audio editing and engineering by ZCross Media.Full show notes and transcript here.

In this week's episode, Adam, Ben, and Carol dive into the nuanced world of software development as they explore the subjectivity inherent in coding.How do personal preferences, team cultures, and individual experiences shape the way code is written, reviewed, and maintained. From debates over naming conventions to the art of code reviews, we unpack the many ways that subjectivity influences technical decisions and the collaborative process.Follow the show and be sure to join the discussion on Discord! Our website is workingcode.dev and we're @workingcode.dev on Bluesky. New episodes drop weekly on Wednesday.And, if you're feeling the love, support us on Patreon.With audio editing and engineering by ZCross Media.Full show notes and transcript here.

In this week's episode, Adam, Ben, and Tim discuss the never ending rabbit hole that is implementing soft deletes in a database. What starts as a simple solution cascades into countless challenges and pitfalls, such as referential integrity, data consistency and compliance. This and other coding crimes in this week's episode.Follow the show and be sure to join the discussion on Discord! Our website is workingcode.dev and we're @workingcode.dev on Bluesky. New episodes drop weekly on Wednesday.And, if you're feeling the love, support us on Patreon.With audio editing and engineering by ZCross Media.Full show notes and transcript here.

In this week's episode, Ben, Carol, and Tim are back to discuss picking the right tool for the right job. More specifically, the value of proportionality in effort and resource allocation, questioning when it's appropriate to cut corners versus maintaining high standards, when you should stick to what you know versus learning something new, and when you should pay more attention to context when making decisions.Follow the show and be sure to join the discussion on Discord! Our website is workingcode.dev and we're @workingcode.dev on Bluesky. New episodes drop weekly on Wednesday.And, if you're feeling the love, support us on Patreon.With audio editing and engineering by ZCross Media.Full show notes and transcript here.

In this week's episode, Adam asks the question: To sync or not to sync? Sparked by an exploration of a competitor's API approach, the team share their thoughts on handling long-running tasks efficiently.Follow the show and be sure to join the discussion on Discord! Our website is workingcode.dev and we're @workingcode.dev on Bluesky. New episodes drop weekly on Wednesday.And, if you're feeling the love, support us on Patreon.With audio editing and engineering by ZCross Media.Full show notes and transcript here.

In this week's episode, the crew discuss the relevance and significance of open-source software in the age of AI. The open source community offers domain expertise, rigorous testing, responsive bug fixing, and community support. But when AI can generate code with proficiency, how does the value calculus change when deciding to install a new package, generate code with an AI, or simply do it yourself?Follow the show and be sure to join the discussion on Discord! Our website is workingcode.dev and we're @workingcode.dev on Bluesky. New episodes drop weekly on Wednesday.And, if you're feeling the love, support us on Patreon.With audio editing and engineering by ZCross Media.Full show notes and transcript here.

To be a good producer you have to be a good consumer. In this week's podcast, the whole team is back to delve into the concept of 'skin in the game' in product development and how consuming your own product, known as “dogfooding”, and empathizing with users can influence the development process.Follow the show and be sure to join the discussion on Discord! Our website is workingcode.dev and we're @workingcode.dev on Bluesky. New episodes drop weekly on Wednesday.And, if you're feeling the love, support us on Patreon.With audio editing and engineering by ZCross Media.Full show notes and transcript here.

In this week's episode, Adam and Ben discuss the notion of “If I'm still telling you what to do in six months, then something went wrong”, a take heard in a recent episode of Lenny's Podcast.How can a company orientate itself to encourage autonomy throughout the career of an engineer? What are reasonable expectations of a junior engineer? These questions and more are discussed in today's episode.Follow the show and be sure to join the discussion on Discord! Our website is workingcode.dev and we're @workingcode.dev on Bluesky. New episodes drop weekly on Wednesday.And, if you're feeling the love, support us on Patreon.With audio editing and engineering by ZCross Media.Full show notes and transcript here.

In this week's episode, Adam and Tim delve into Gemini CLI, a command line interface tool for AI by Google, test-driving it on real code to find its capabilities and limitations.Follow the show and be sure to join the discussion on Discord! Our website is workingcode.dev and we're @workingcode.dev on Bluesky. New episodes drop weekly on Wednesday.And, if you're feeling the love, support us on Patreon.With audio editing and engineering by ZCross Media.Full show notes and transcript here.

In this week's episode, the full crew is back to talk about practical replatforming. In past episodes we've discussed replatforming in a more abstract sense, but Adam has much to share about ongoing real-world replatforming at AlumniQ. When the rubber meets the road, certain realities and complexities, which may not be obvious, may affect decision-making and replatforming strategy.Follow the show and be sure to join the discussion on Discord! Our website is workingcode.dev and we're @workingcode.dev on Bluesky. New episodes drop weekly on Wednesday.And, if you're feeling the love, support us on Patreon.With audio editing and engineering by ZCross Media.Full show notes and transcript here.

In this week's episode, the team gets into it with special guest Dan Wilson, an AI & tech consultant that has recently created free and paid courses on using AI in daily workflows. They also dig into the ins and outs of creating Udemy courses and their viability in the tech space.Dan's courses:Master ChatGPT: Build AI Assistants That Know Your Business (FREE)Generative AI for Developers: How To Use AI In Your Workday (Use code quackquack for a special discount)Follow the show and be sure to join the discussion on Discord! Our website is workingcode.dev and we're @workingcode.dev on Bluesky. New episodes drop weekly on Wednesday.And, if you're feeling the love, support us on Patreon.With audio editing and engineering by ZCross Media.Full show notes and transcript here.

In this week's episode, the team dives into a potluck of topics including the effective usage of Large Language Models (LLMs) by feeding their ego, the excitement of implementing feature flags in development cycles, and further developments and opportunities with Adam's side hustle app "Jump Run" the journey of building a side hustle with 'Jump Run'.Follow the show and be sure to join the discussion on Discord! Our website is workingcode.dev and we're @workingcode.dev on Bluesky. New episodes drop weekly on Wednesday.And, if you're feeling the love, support us on Patreon.With audio editing and engineering by ZCross Media.Full show notes and transcript here.

In this week's episode, the crew is back to discuss and question quickly shifting values in the world and their implications for developers. Will AI erode the importance of code craftsmanship? When old values are quickly discarded, what does that say about the legitimacy of the new values? Is human coding obsolescence the elephant in the room?Follow the show and be sure to join the discussion on Discord! Our website is workingcode.dev and we're @workingcode.dev on Bluesky. New episodes drop weekly on Wednesday.And, if you're feeling the love, support us on Patreon.With audio editing and engineering by ZCross Media.Full show notes and transcript here.