
Hosted by William · EN
Giving Claude Code a voice, so we can discuss best practices, risks, assumptions, etc,

AI coding tools are excellent at adding code and terrible at telling you what that code will cost you later. Every generated helper, wrapper, and convenience layer quietly increases the number of things that must be true for your system to work, and by the time you notice, the cheapest path forward is always to add one more layer instead of removing any. This episode names that trap, the dependency gravity well, and gives builders a way to see it forming while the escape is still cheap. Produced by VoxCrea.AIThis episode is part of an ongoing series on governing AI-assisted coding using Claude Code.👉 Each episode has a companion article — breaking down the key ideas in a clearer, more structured way. If you want to go deeper (and actually apply this), read today’s article here: 𝐂𝐥𝐚𝐮𝐝𝐞 𝐂𝐨𝐝𝐞 𝐂𝐨𝐧𝐯𝐞𝐫𝐬𝐚𝐭𝐢𝐨𝐧𝐬 At aijoe.ai, we build AI-powered systems like the ones discussed in this series. If you’re ready to turn an idea into a working application, we’d be glad to help.

AI coding tools solve problems the way the training data solved them, which usually means reaching for a library instead of writing twenty lines. Ask for a retry wrapper and you get tenacity, ask for date math and you get arrow, ask for a config loader and you get three transitive packages you never evaluated. This episode looks at how AI-assisted development quietly expands your dependency surface, why the cost shows up months later in upgrades, audits, and breakage, and what a builder actually has to own to keep it in check. Produced by VoxCrea.AIThis episode is part of an ongoing series on governing AI-assisted coding using Claude Code.👉 Each episode has a companion article — breaking down the key ideas in a clearer, more structured way. If you want to go deeper (and actually apply this), read today’s article here: 𝐂𝐥𝐚𝐮𝐝𝐞 𝐂𝐨𝐝𝐞 𝐂𝐨𝐧𝐯𝐞𝐫𝐬𝐚𝐭𝐢𝐨𝐧𝐬 At aijoe.ai, we build AI-powered systems like the ones discussed in this series. If you’re ready to turn an idea into a working application, we’d be glad to help.

AI coding tools are excellent at stateless code, a function that takes inputs and returns outputs with no memory of what came before. They are noticeably worse at code that has to remember things: retry counters, partial completions, queue positions, resumable pipelines, anything where correctness depends on what already happened. This episode explains why that gap exists, why it does not close with a bigger model, and what the builder has to own instead. Produced by VoxCrea.AIThis episode is part of an ongoing series on governing AI-assisted coding using Claude Code.👉 Each episode has a companion article — breaking down the key ideas in a clearer, more structured way. If you want to go deeper (and actually apply this), read today’s article here: 𝐂𝐥𝐚𝐮𝐝𝐞 𝐂𝐨𝐝𝐞 𝐂𝐨𝐧𝐯𝐞𝐫𝐬𝐚𝐭𝐢𝐨𝐧𝐬 At aijoe.ai, we build AI-powered systems like the ones discussed in this series. If you’re ready to turn an idea into a working application, we’d be glad to help.

Experienced engineers have a well-tuned instinct for where bugs hide in human-written code, and that instinct misfires badly on AI output. They line-audit the boring mechanical code the model almost never gets wrong, then wave through the plausible-looking integration logic and error handling where it actually fails. This episode maps where AI-generated code is genuinely reliable versus genuinely dangerous, so builders can stop spending their review budget in the wrong places. Produced by VoxCrea.AIThis episode is part of an ongoing series on governing AI-assisted coding using Claude Code.👉 Each episode has a companion article — breaking down the key ideas in a clearer, more structured way. If you want to go deeper (and actually apply this), read today’s article here: 𝐂𝐥𝐚𝐮𝐝𝐞 𝐂𝐨𝐝𝐞 𝐂𝐨𝐧𝐯𝐞𝐫𝐬𝐚𝐭𝐢𝐨𝐧𝐬 At aijoe.ai, we build AI-powered systems like the ones discussed in this series. If you’re ready to turn an idea into a working application, we’d be glad to help.

AI coding tools produce code that works and reads fine in isolation, but the names they choose are locally plausible and globally inconsistent. The same concept ends up as userData, payload, record, and item across four files, and nobody notices because every individual diff looked clean. This episode makes the case that naming drift is the highest interest debt in AI-assisted codebases, because names are the index your future self and your next AI session both search against. Produced by VoxCrea.AIThis episode is part of an ongoing series on governing AI-assisted coding using Claude Code.👉 Each episode has a companion article — breaking down the key ideas in a clearer, more structured way. If you want to go deeper (and actually apply this), read today’s article here: 𝐂𝐥𝐚𝐮𝐝𝐞 𝐂𝐨𝐝𝐞 𝐂𝐨𝐧𝐯𝐞𝐫𝐬𝐚𝐭𝐢𝐨𝐧𝐬 At aijoe.ai, we build AI-powered systems like the ones discussed in this series. If you’re ready to turn an idea into a working application, we’d be glad to help.

When a company says most of its production code is model written, the number sounds like a verdict on engineers. It is not. The 80% figure measures typing, not deciding, and the interesting question is what the remaining 20% actually consists of, because that is where the job moved. This episode breaks down what a claim like that can and cannot tell you, and what changes in your week if it is true at your company too. Produced by VoxCrea.AIThis episode is part of an ongoing series on governing AI-assisted coding using Claude Code.👉 Each episode has a companion article — breaking down the key ideas in a clearer, more structured way. If you want to go deeper (and actually apply this), read today’s article here: 𝐂𝐥𝐚𝐮𝐝𝐞 𝐂𝐨𝐝𝐞 𝐂𝐨𝐧𝐯𝐞𝐫𝐬𝐚𝐭𝐢𝐨𝐧𝐬 At aijoe.ai, we build AI-powered systems like the ones discussed in this series. If you’re ready to turn an idea into a working application, we’d be glad to help.

The promise of AI-assisted building is that you no longer need to know the domain, the model knows it for you. In practice the opposite is true: the less you know about a domain, the more confidently wrong AI output you will ship, because you cannot tell the difference between an answer that is correct and an answer that merely sounds correct. This episode makes the case that domain expertise is not what AI replaces, it is the thing that makes AI usable at all, and it gives builders a concrete way to work in domains where they are not yet the expert. Produced by VoxCrea.AIThis episode is part of an ongoing series on governing AI-assisted coding using Claude Code.👉 Each episode has a companion article — breaking down the key ideas in a clearer, more structured way. If you want to go deeper (and actually apply this), read today’s article here: 𝐂𝐥𝐚𝐮𝐝𝐞 𝐂𝐨𝐝𝐞 𝐂𝐨𝐧𝐯𝐞𝐫𝐬𝐚𝐭𝐢𝐨𝐧𝐬 At aijoe.ai, we build AI-powered systems like the ones discussed in this series. If you’re ready to turn an idea into a working application, we’d be glad to help.

Technical debt used to come from shortcuts in implementation. With AI, the debt moves upstream: the code is clean, tested, and idiomatic, but it solves a slightly wrong problem because the specification in your prompt was incomplete. This episode names that failure mode, specification debt, and shows why it compounds faster than ordinary technical debt and is much harder to see in review. Produced by VoxCrea.AIThis episode is part of an ongoing series on governing AI-assisted coding using Claude Code.👉 Each episode has a companion article — breaking down the key ideas in a clearer, more structured way. If you want to go deeper (and actually apply this), read today’s article here: 𝐂𝐥𝐚𝐮𝐝𝐞 𝐂𝐨𝐝𝐞 𝐂𝐨𝐧𝐯𝐞𝐫𝐬𝐚𝐭𝐢𝐨𝐧𝐬 At aijoe.ai, we build AI-powered systems like the ones discussed in this series. If you’re ready to turn an idea into a working application, we’d be glad to help.

AI can produce a working feature in minutes, but when that feature breaks, the debugging session often runs longer than writing the code from scratch would have. The reason is not that AI code is worse, it is that you never built a mental model of it. This episode names the hidden cost that shows up two weeks after the fast win, and gives builders a way to pay it down before it compounds. Produced by VoxCrea.AIThis episode is part of an ongoing series on governing AI-assisted coding using Claude Code.👉 Each episode has a companion article — breaking down the key ideas in a clearer, more structured way. If you want to go deeper (and actually apply this), read today’s article here: 𝐂𝐥𝐚𝐮𝐝𝐞 𝐂𝐨𝐝𝐞 𝐂𝐨𝐧𝐯𝐞𝐫𝐬𝐚𝐭𝐢𝐨𝐧𝐬 At aijoe.ai, we build AI-powered systems like the ones discussed in this series. If you’re ready to turn an idea into a working application, we’d be glad to help.

Most teams treat hallucination as a prompt problem, something you fix with better instructions or a bigger model. But in production, hallucination is a systems problem. The builders shipping reliable AI have stopped trying to make the model stop lying and started building verification layers that assume it will. This episode is about designing those layers, what actually catches a confident wrong answer before it reaches a user, and why most verification setups fail silently. Produced by VoxCrea.AIThis episode is part of an ongoing series on governing AI-assisted coding using Claude Code.👉 Each episode has a companion article — breaking down the key ideas in a clearer, more structured way. If you want to go deeper (and actually apply this), read today’s article here: 𝐂𝐥𝐚𝐮𝐝𝐞 𝐂𝐨𝐝𝐞 𝐂𝐨𝐧𝐯𝐞𝐫𝐬𝐚𝐭𝐢𝐨𝐧𝐬 At aijoe.ai, we build AI-powered systems like the ones discussed in this series. If you’re ready to turn an idea into a working application, we’d be glad to help.