The Programming Podcast

Everyone's vibe coding their way to broken software. More AI doesn't fix a bad foundation, it just makes the mess louder and faster! You've been told AI makes you 10x more productive. So why does it feel like you're drowning?In this episode, Danny Thompson, Leon Noel, and GitKraken's Chris Griffing and Jeremy Castile break down what AI workflows actually look like at a senior level, the context docs, the architecture guardrails, the multi-agent orchestration, and the research data behind why 84% of developers feel more productive (and why the other 16% are probably doing it wrong).Plus: the one thing Danny does after every successful AI session that multiplies the value of every token he's ever spent.Check out GitKraken at https://www.gitkraken.com/Follow Jeremy Castile! https://www.linkedin.com/in/jeremycastile/Follow Chris Griffinghttps://www.linkedin.com/in/cmgriffing/https://x.com/cmgriffingGet The Developers Guide To AI here! http://developersguide.ai/✅ If you made it to the end, comment: “Shine bright like a GitHub Star!” so we know who is a real one!https://www.commityourcode.com/Come to CYC!Get The Developers Guide To AI here!http://developersguide.ai/Stay in Touch:📧 Have ideas or questions for the show? Or are you a business that wants to talk business?Email us at dannyandleonspodcast@gmail.com!Danny Thompsonhttps://x.com/DThompsonDevhttps://www.linkedin.com/in/DThompsonDevwww.DThompsonDev.comLeon Noelhttps://x.com/leonnoelhttps://www.linkedin.com/in/leonnoel/https://100devs.org/📧 Have ideas or questions for the show? Or are you a business that wants to talk business?Email us at dannyandleonspodcast@gmail.com!00:00 AI Amplifies Whatever Workflow You Already Have01:29 Meet the Hosts & Guests02:37 What AI Tools Are We Actually Using?06:07 Danny's Architecture-First Approach10:19 Leon's Burnout Warning & Workflow Honesty12:00 What AI Has Unlocked (and What It Hasn't)17:43 GitKraken's Research: The Code Churn Problem19:41 84% of Developers Feel More Productive — Here's Why21:52 The Three Cohorts: Assistive → Emerging → Agent Native23:32 Leon's Raw Take: Middle Manager Extreme25:09 The Bottleneck Has Shifted (It's No Longer the Code)27:12 GitKraken Kepler: The Agentic Development Environment30:57 Managing Multiple Agents Like a Team33:29 How Do You Stay Updated Across All Your Agents?36:45 Is This For Everyone or Just Enterprise?39:27 Danny's #1 Tip: The Context Doc Strategy42:22 How to Fight Context Rot46:17 Git Workflow When Running Multiple Agents49:50 Structured Files: Code Standards, UI Docs, Deviation Files51:15 Question of the Day: Which AI Tool Would You Miss Most?57:01 Closing

Apple’s latest decision to team with Google and use Gemini signals something bigger than a headline. It highlights how far Gemini has come, and why utility is becoming the real battleground for AI in 2026.In this episode, we sit down with Logan Kilpatrick from the Gemini team at Google DeepMind to talk about what this moment means for developers, builders, and teams choosing tools today. We get into the evolution of Gemini, why multimodality and long context mattered early, and how Gemini is increasingly showing up where people already work through products like Workspace, Gmail, and Docs.✅ If you made it to the end, comment: “Documentation Traffic.” so we know who is a real one!SITE https://www.programmingpodcast.com/Stay in Touch:📧 Have questions for the show? Or are you a business that wants to talk business?Email us at dannyandleonspodcast@gmail.com!Danny Thompsonhttps://x.com/DThompsonDev / dthompsondev www.DThompsonDev.comLeon Noelhttps://x.com/leonnoel / leonnoel https://100devs.org/📧 Have questions for the show? Or are you a business that wants to talk business?Email us at dannyandleonspodcast@gmail.com!Subscribe if you want honest, no-hype conversations about where software development is heading in 2026.We also dig into what’s next for image generation and editing, including the leap in text accuracy, practical features creators want (like layers and transparent backgrounds), and the role of technologies like SynthID in building trust as AI content becomes more common.Plus: vibe coding, reasoning models, prompt expansion, how developers can ask for more ambitious outcomes, and why proactivity and proof-of-work experiences are shaping the next wave of AI products.If you’re building with AI or trying to stay ahead as a developer, this episode will give you a clear view into where things are going.0:00 Apple’s decision changes the AI narrative1:11 Meet today’s guest: Logan Kilpatrick (Gemini team)1:52 Apple quote and why this is big for Gemini2:19 Are the model wars over, and are utility wars next?4:20 Gemini in real workflows: Workspace, Gmail, and daily utility5:26 AI hype vs reality: why products must meet users where they are6:42 Balancing frontier progress with “do not break the product” responsibility8:25 Nano Banana and the leap in text accurate images9:28 Infographics, presentations, and where image generation is going10:00 Why text rendering became a key metric for model quality12:19 What users want next: transparent backgrounds, layers, better editing13:52 Trust and safety: SynthID, watermarking, and standardization challenges16:06 What developers ask for most: quota and scale17:38 Logs and the idea of an agent that finds missing product features19:31 How people should use AI differently: native form factors, proactivity21:19 Proof of work and why Deep Research builds trust fast24:53 Prompt expansion, reasoning models, and why “prompt wizardry” is fading26:40 Ask for more: why ambition is now the best prompting strategy29:36 Frameworks vs over optimizing prompts: when it matters, when it does not32:52 What “vibe coding” means now and how it is evolving34:08 Teaching vibe coding on day one of school36:01 Ask Danny, Leon, and Logan: feeling behind in tech39:02 The moving finish line, authenticity, and turning the gap into a roadmap41:25 Closing

It’s 2026. If you want to learn how to code and actually get results, this episode is your roadmap.Danny and Leon break down the stuff that is not “cool advice,” but is the advice that gets people hired. We talk about why course-hoarding feels productive but is not, what the real bottleneck in tech actually is (hint: not syntax), and how to build a learning system that survives the trough of sorrow.You’ll walk away with:The 3-part foundation that decides if you stick with codingWhy “problem solving” is the real job, not typing codeWhen AI helps, and when it quietly ruins your learningThe learning science that separates dabblers from finishers (active recall + spaced repetition)How to pick what to learn based on your local market (and stop wasting years)Why community is the cheat code that keeps you moving when motivation diesIf your goal is to learn to code this year, do one action right now: join a community, pick a path, and start.✅ If you made it to the end, comment: “In 2026 I’m gonna grow my skill set.”SITE https://www.programmingpodcast.com/Stay in Touch:📧 Have questions for the show? Or are you a business that wants to talk business?Email us at dannyandleonspodcast@gmail.com!Danny Thompsonhttps://x.com/DThompsonDev / dthompsondev www.DThompsonDev.comLeon Noelhttps://x.com/leonnoel / leonnoel https://100devs.org/📧 Have questions for the show? Or are you a business that wants to talk business?Email us at dannyandleonspodcast@gmail.com!Chapters00:00 - The 2026 promise: real results, not cool advice01:56 - Why you should listen to us (and why this episode goes viral)04:18 - Start with your “why” or you will quit05:45 - The 3 foundations: manage frustration, consistency, take care of yourself09:11 - What companies pay for: problem solving, not syntax12:30 - The shiny becomes dull: how people quit when novelty fades15:49 - Build to derisk yourself: projects that help vs projects that hurt17:15 - The trough of sorrow and crash of ineptitude18:51 - AI as the easy exit, and why you cannot take it21:09 - Hot take: earn AI later, do not use it early22:46 - Over-reliance makes you weaker (and why teams sometimes remove AI)25:36 - Learn how to learn: Barbara Oakley and rebuilding your foundation26:45 - Active recall: do less work, remember more27:45 - Spaced repetition: stop forgetting what you learn30:11 - Build projects early to create incentive and momentum32:25 - Make concepts “sticky” with analogies and mental models33:31 - Your first year on the job decides career vs job35:37 - Stop asking for “the tech stack” and start reading your local market38:40 - Dallas example: 400 MERN jobs vs 34,000 Java jobs42:31 - No one is taking risks right now: prove you can hit the ground running44:16 - Target companies strategically (emerging talent programs, hiring volume)47:00 - Do not marry a stack, marry adaptability48:49 - System rules: make every project your own, break goals into daily actions51:38 - Pick one path and finish: FreeCodeCamp, Odin Project, 100Devs, Full Stack Open52:42 - The real cheat code: community56:31 - Motivation expires, community keeps you moving59:44 - Talent is distributed, opportunity is not1:03:28 - Take action right now: join a community1:04:34 - Comment to prove you are a real one1:04:56 - “I don’t have time” and the priority truth1:06:10 - Your value in 2026: caring, context, judgment, and composing solutions

We caught a massive production error during the new Steam Machine launch that exposed internal database IDs and undefined variables to the public. In this episode, we break down exactly what went wrong, how a simple try/catch or React Error Boundary could have saved them, and why "testing in production" is terrifying when millions of dollars are on the line.Plus, we answer a listener's question about getting stuck on "perfecting" projects. Danny explains why building a "Discord Clone" might actually be hurting your resume and why you need to stop obsessing over your navbar and just SHIP.SITE https://www.programmingpodcast.com/💡 Sponsor: Level Up Financial PlanningChanging careers or increasing your income? Get financial clarity with Level Up Financial Planning—helping early and mid-career tech professionals secure their financial future. Visit LevelUpFinancialPlanning.com for a free consultation!https://www.levelupfinancialplanning.com/Stay in Touch:📧 Have questions for the show? Or are you a business that wants to talk business?Email us at dannyandleonspodcast@gmail.com!Danny Thompsonhttps://x.com/DThompsonDevhttps://www.linkedin.com/in/DThompsonDevwww.DThompsonDev.comLeon Noelhttps://x.com/leonnoelhttps://www.linkedin.com/in/leonnoel/https://100devs.org/📧 Have questions for the show? Or are you a business that wants to talk business?Email us at dannyandleonspodcast@gmail.com!In this episode:The Steam Machine Incident: How a launch page leaked internal naming conventions.Frontend Defense: Using Zod, Optional Chaining, and Error Boundaries to fail gracefully.The "Clone" Trap: Why recruiters don't care about your Discord clone (and what to build instead).The 95% Rule: How to stop letting small features kill big projects.Chapters: 0:00 - The Steam Machine Production Error 03:15 - Leaking Database IDs & Console Logs 06:28 - The Fix: React Error Boundaries & Fallback UIs 10:50 - Frontend Defense: Optional Chaining, Zod & Defaults 13:06 - Sponsor: Level Up Financial Planning 15:32 - The Power of Try/Catch & Environment Variables 18:57 - Root Cause Analysis: How did this hit Prod? 26:19 - HackerOne & Getting Paid for Bugs 29:50 - Q&A: "I can't finish my projects" (The Navbar Trap) 37:36 - Why "Clone Projects" Are Hurting Your Resume 41:00 - Conclusion: Let it die on a small feature

“I f*cking give up. May these companies rot.”That one Reddit post cracked open the real state of the 2025 tech job market. Why are Master’s degree grads and senior engineers going months without a single offer, while others are quietly doubling their income with one strategic question?SITE https://www.programmingpodcast.com/💡 Sponsor: Level Up Financial PlanningChanging careers or increasing your income? Get financial clarity with Level Up Financial Planning—helping early and mid-career tech professionals secure their financial future. Visit LevelUpFinancialPlanning.com for a free consultation!https://www.levelupfinancialplanning.com/Stay in Touch:📧 Have ideas or questions for the show? Or are you a business that wants to talk business?Email us at dannyandleonspodcast@gmail.com!Danny Thompsonhttps://x.com/DThompsonDevhttps://www.linkedin.com/in/DThompsonDevwww.DThompsonDev.comLeon Noelhttps://x.com/leonnoelhttps://www.linkedin.com/in/leonnoel/https://100devs.org/📧 Have ideas or questions for the show? Or are you a business that wants to talk business?Email us at dannyandleonspodcast@gmail.com!In this episode, Leon and I break down why applying to big tech has turned into The Hunger Games, the hidden way internal hiring blocks you before you even start, and the psychological “Pattern Disrupt” technique that makes recruiters remember you instantly — even in a market that’s drowning in resumes.Your code gets you into the room.Your communication keeps you in the seat.If you want to survive this market, silence is no longer an option.TIMESTAMPS0:00 – The Crisis: “May These Companies Rot”1:26 – The Reddit Post That Broke The Internet6:50 – The “Trough of Sorrow” & The 1-in-60 Rule11:55 – The Google Trap (3.3M Applicants for 5k Jobs)16:42 – The Truth About Internal Hiring & “Soft No’s”22:00 – The “Pattern Disrupt”: How To Hack The Interview30:00 – The Pickleball Strategy (Networking Without Being Cringe)41:30 – Rejection Therapy: Training Your Brain at Starbucks49:00 – “Pre-Season” Prep: Why You Are Failing Technical Rounds55:00 – Case Study: How She Doubled Her Income Overnight58:34 – “You Are Not Saint Jude” (Stop Donating Your Skills)

You did everything you were “supposed” to do. You climbed from junior to senior to staff to principal. You have the title, the salary, the prestige, and a calendar full of meetings. And somehow, you feel empty. You are highly paid, deeply experienced, and still sitting at your keyboard wondering, “What should my fingers actually be doing right now?”Stay in Touch:📧 Have ideas or questions for the show? Or are you a business that wants to talk business?Email us at dannyandleonspodcast@gmail.com!Danny Thompsonhttps://x.com/DThompsonDevhttps://www.linkedin.com/in/DThompsonDevwww.DThompsonDev.comLeon Noelhttps://x.com/leonnoelhttps://www.linkedin.com/in/leonnoel/https://100devs.org/📧 Have ideas or questions for the show? Or are you a business that wants to talk business?Email us at dannyandleonspodcast@gmail.com!In this episode, Danny and Leon dig into what happens when the dream job stops feeling like a dream. They talk about the loss of that early-career magic, the tension between strategy and hands-on building, and why so many principal and staff engineers quietly feel stuck, bored, or like frauds. You will hear how to think about the value of your time, how to shift from “hero developer” to multiplier, and how to build systems, cultures, and people instead of just features.They also tackle the difference between impostor syndrome and an apathy crisis, how to keep your skills sharp without clinging to every ticket, and how to design a team culture where learning and ownership are normal. In the Ask Danny and Leon segment, they close with a deep dive on job search frustration, referrals that still end in rejection, why your resume and presence are probably working against you, and how to use volume, networking, and better communication to actually see results.Perfect for principal, staff, and senior engineers who feel like they have made it and yet feel miserable, and for earlier career devs who want to avoid ending up in the same place.Chapters00:00 – The principal engineer who feels lost02:15 – Remembering the first time code felt like magic07:25 – The three types of senior engineers10:30 – What your time really costs at the principal level16:10 – Trading magic for meetings and how to get it back19:00 – Scaling yourself through docs, videos, and systems20:45 – Building a culture of experiments and continuous learning22:30 – Aligning the team on mission, not just tickets23:30 – This isn’t impostor syndrome, it’s an apathy crisis24:30 – Becoming a multiplier instead of the hero developer29:40 – Turning your engineers into teachers and leaders32:50 – The five levels of decision autonomy35:30 – Nobody actually knows everything (and that’s okay)35:55 – Ask Danny & Leon: “I have zero prospects, when will I see results?”40:20 – Referrals, rejections, and why volume still wins44:50 – Your resume doesn’t read like a human story49:50 – Visibility, effort, and the gas station promotion story53:40 – Technical skill is not your whole career56:00 – Coffee chats, calendars, and how activity predicts outcomes59:00 – Effort over luck and closing thoughts

You know that “it’s a simple fix” task that eats your entire sprint? If you liked this episode or if this saved you a sprint: like, subscribe, and share with your team. Comment your worst “simple fix” story! We’ll feature a few next episode!This episode is about going from “just parse the RSS” to a real system with cron jobs, a database, SSR, caching, pagination, title-matching pain, and a YouTube Data API gotcha where deleted videos still show up and break your counts. We unpack the technical rabbit hole, the product/process mistakes that made it worse, and the practical fixes you can ship today.SITE https://www.programmingpodcast.com/Stay in Touch:📧 Have ideas or questions for the show? Or are you a business that wants to talk business?Email us at dannyandleonspodcast@gmail.com!Danny Thompsonhttps://x.com/DThompsonDevhttps://www.linkedin.com/in/DThompsonDevwww.DThompsonDev.comLeon Noelhttps://x.com/leonnoelhttps://www.linkedin.com/in/leonnoel/https://100devs.org/📧 Have ideas or questions for the show? Or are you a business that wants to talk business?Email us at dannyandleonspodcast@gmail.com!Highlights- Why YouTube RSS only returns ~15 items, and when to switch to the Data API-The sneaky “deleted video” entries that broke episode matching (and the 4-line filter that fixed it)- Cron + DB to avoid on-request parsing delays, with lazy loading/pagination for perf- Levenshtein vs. AI scraping for cross-platform title matching (and tradeoffs)- SSR for SEO: hydration pitfalls, view-source reality checks, and caching strategy- Process: ticket sizing gone wrong, sprint rituals that would’ve saved weeks, and a fallback plan when APIs fail- Career bit (Huntober): the highest-ROI job-hunt moves—ask directly for referrals and quantify your wins so AI can actually write a good resumeWhat You’ll LearnWhen RSS is fine—and when you must use YouTube Data API v3Designing a resilient ingestion path (cron triggers, rate limits, cost control)Secure API key handling and avoiding accidental exposureConcrete heuristics for matching episodes across platformsThe “fallback first” mindset when upstream services go downStack & Tools MentionedNext.js/SSR, Tailwind/CSS (retro radio UI), cron + DB ingest, YouTube Data API v3, Spotify RSS, Levenshtein distance, AI/LLM parsing workflow, lazy loading/pagination, caching.Chapters00:00 It’s “simple”… until it isn’t (cold open)02:00 50 episodes milestone + data-driven intros03:20 New personal site goals (personas, UX, content routing)06:04 Rotary-dial content hub idea07:42 Plan A: “Just use Spotify/YouTube RSS”08:56 Parsing delays → cron + DB ingest11:00 Release cadence (Thurs AM CT) & autosync plan12:07 YouTube RSS ≈ 15 items?!13:19 Enabling YouTube Data API v3 (the missing step)14:22 Title matching fails; publish vs. upload date mismatch16:31 AI scrape workflow vs. deterministic pipelines17:13 Levenshtein distance for fuzzy matching18:53 The painful bug: deleted YouTube videos still in API20:20 Security considerations for API keys21:08 Retro CSS “radio” UI + Tailwind23:01 From 2 points to full sprint (scope creep lessons)24:03 Rate limits, CORS, and API cost control24:54 SSR for SEO, hydration errors, caching26:24 Web creativity is back (experimentation talk)27:29 Sprint Zero / refactor time that saves real sprints28:24 Resilience: API fallback to RSS29:18 Perf: lazy loading & pagination30:01 Tests vs. cowboy deploys (real talk)31:20 Takeaways: when to keep it simple vs. do it right36:01 What is Huntober?37:41 Highest-ROI job hunt move: ask for referrals39:07 Make AI useful: quantify your work41:15 Outro

Senior engineers don’t “wing it.” They use mental models to turn plans into production—faster, safer, and with less drama. Danny Thompson, Leon Noel, and Kent C. Dodds break down the exact models they use: decision docs, second-order thinking, reducing cognitive load, Occam’s Razor, leaky abstractions, feature flags vs. staging, chaos engineering, AI context windows (and rot), MCP, onboarding docs, blind code reviews, and more. If you’re pushing from mid → senior (or trying to sound senior in interviews), steal these.Guest: Kent C. Dodds!https://kentcdodds.com/https://x.com/kentcdodds @KentCDodds-vids SITE https://www.programmingpodcast.com/Stay in Touch:📧 Have ideas or questions for the show? Or are you a business that wants to talk business?Email us at dannyandleonspodcast@gmail.com!Danny Thompsonhttps://x.com/DThompsonDevhttps://www.linkedin.com/in/DThompsonDevwww.DThompsonDev.comLeon Noelhttps://x.com/leonnoelhttps://www.linkedin.com/in/leonnoel/https://100devs.org/📧 Have ideas or questions for the show? Or are you a business that wants to talk business?Email us at dannyandleonspodcast@gmail.com!You’ll learn→ How to communicate invisible work like a senior (impact vs activity)→ Decision documents: making tradeoffs explicit→ Second-order thinking to prevent “future bugs”→ When to ship fast with flags vs. slow with staging→ Designing for onboarding—humans and AI assistants→ Using AI without nuking your circle of competence→ Local job tactics (Memphis example), recruiters, and “entry-level” framingIf this helped, hit 👍 and subscribe. Drop your favorite mental model in the commentsChapters00:00 Cold open — “When plans break in prod”00:36 Why mental models matter for seniors02:45 Define “mental model” (map vs. territory)05:22 Intros + episode setup07:05 Decision documents & guiding principles10:48 Coaching moments: easy vs. right solutions12:56 Second-order thinking (caching, short links, spam)15:58 Occam’s Razor in real engineering decisions18:12 Onboarding for Future-You (and your AI)20:44 Tests as guardrails for humans + LLMs22:18 AI context windows, “context rot,” and structure24:55 Circle of competence in the AI era27:18 Should juniors use AI? The real risks30:06 Shipping fast vs. learning deep: when to limit AI31:55 Interviews are changing: system design vs LeetCode33:42 Confidence traps: getting gaslit by your prompts36:00 Too many abstractions → leaky abstractions38:40 Blind code reviews & cross-team learning41:20 Google-style anonymous reviews (tradeoffs)44:00 Feature flags vs. staging (the spicy debate)46:52 Chaos engineering & safe rollouts in prod49:10 Pragmatism over dogma: what actually ships50:58 Kent’s Epic AI cohort & MCP primer54:20 Listener Q&A: local vs. remote, .NET vs. Node1:00:45 Ask Danny, Leon, And Kent!