The Programming Podcast

A debate on whether learning coding fundamentals still matters in the age of AI. They explore how AI changes hiring, the rise of AI-augmented junior engineers, and when relying on AI creates bugs. Practical roadmaps and warnings about using AI too early round out the conversation.

LeetCode is dead… or is it?HackerRank dropped a bold take that set the internet on fire: “LeetCode is dead,” because devs do not write code line-by-line anymore. We orchestrate AI, debug its output, and catch failures in real time. So if the job changed, should interviews finally change too?💡 Sponsor: Huge shoutout to Auth0!Secure AI agents, humans, and whatever comes nexthttps://auth0.com/In this episode, Danny Thompson and Leon Noel break down what HackerRank is really saying, why LeetCode traffic is still exploding, and what the “new interview” is starting to test: fundamentals plus AI fluency.We talk about the lag you should expect from big companies, how to think about DSA strategically (especially if you are not targeting FAANG), and what modern AI competency looks like in practice. Prompting is not typing faster. It is context engineering. Question, not command.Then we tackle a listener question: “I’m a junior dev and my job doesn’t use any tools that make me competitive. How do I level up in AI?” The answer is direct: growth is not guaranteed at work, so you have to build it yourself. Tools, models, workflows, and habits that keep you ahead.If you are prepping for interviews in 2026, this is your roadmap for what to keep, what to drop, and what to add.✅ 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.Chapters (YouTube)0:00 HackerRank says “LeetCode is dead”1:15 Welcome + intros (Danny Thompson, Leon Noel)1:55 Danny’s Atlassian update: Forge, Marketplace reach, and what’s coming3:26 Why this HackerRank post matters (they have the hiring data)4:34 Interviews must evolve: testing AI usage, not just algorithms5:14 HackerRank’s AI IDE idea: evaluating prompts and process6:34 “LeetCode isn’t dead” counterpoint: traffic is climbing again7:24 Why adoption lags: companies will keep old interviews for years9:12 Practical strategy: DSA still opens doors, but it’s not the only door10:59 Sponsor: Auth0 (identity for AI agents)11:46 FAANG vs non-FAANG prep: how deep you actually need to go13:03 Some companies “think they’re FAANG” and what that signals13:52 Interview mindset shift: show everything, don’t hope they notice15:57 The new skill set: fundamentals + AI fluency16:31 Why most people think AI “sucks” and how to fix it18:05 The core: context before commands (index first, act second)20:35 Vibe coding vs AI engineering: the difference is the setup21:45 Transactional prompting trap + the “drop shadow” example23:09 Use AI like a blunt senior engineer to challenge your assumptions25:00 “Question, not command” as a simple upgrade25:36 The new layer: tools, agents, MCPs, workflows, AI-augmented engineering27:42 Internal knowledge tools (Rovo) and why focused context wins29:25 Ask Danny & Leon: “My job doesn’t use AI tools. How do I stay competitive?”29:57 “Learning doesn’t happen on the job” and how to level up outside work31:10 Try models, tools, and agentic workflows (Cursor, etc.)32:06 Bring the value back to work: prove productivity, then ask for adoption33:00 Your circle changes your ceiling (community as a force multiplier)35:09 A job dictates pay, you dictate worth36:19 Closing: keep learning, keep growing, see you next episode

Monica Bajaj, VP of Engineering at Okta who builds identity and secure AI architectures, warns about autonomous agents running wild. She unpacks probabilistic runtimes, accidental cloud costs, the “infinite loop” that can bankrupt teams, and a Purpose-Privilege-Protection playbook with token vaults gateways and circuit breakers to stop runaway behavior.

A rapid breakdown of two surprise model releases and what a 1‑million‑token context window means for developer workflows. They explore agent teams and orchestration tradeoffs. There's a deep dive into tooling like Playwright and how massive context changes code scanning. They also cover a recent security blunder from vibe coding and whether website builders or custom code suit small businesses.

A lively take on Karpathy's claim that coding workflows shifted to agent-driven work. They react to English-first programming, agentic automation and sleeping agents. Conversation covers the builder vs idea-person shift, risks of skill atrophy, and a looming flood of messy AI-generated code. They also explore new tooling and what 2026 might bring for software work.

Logan Kilpatrick, who leads developer products at Google DeepMind for AI Studio and the Gemini API, joins to discuss Gemini’s rise and what Apple’s choice signals. They cover Gemini’s multimodal strengths, Workspace integrations that boost daily utility, advances in image text accuracy and editing, trust tools like SynthID, and how developers can leverage reasoning models and proactive AI in products.

Is Tailwind facing its demise or is it part of a larger shift? The hosts explore a significant decline in documentation traffic due to AI, undermining revenue streams for open-source projects. They discuss Stack Overflow's startling drop in activity and the community's transition to friendlier platforms like Discord. Concerns emerge over how new developers can find mentorship and verify information in an AI-dominated landscape. The conversation reveals the crucial need for active human communities to navigate the future of software development.

In 2026, learning to code requires practical strategies over trendy advice. Discover why problem-solving is prioritized over syntax in hiring decisions. Learn the importance of building a supportive community to maintain motivation during tough times. Active recall and spaced repetition can revolutionize your retention. Understand local job markets to avoid wasteful learning paths. Finally, establish daily goals and custom projects to drive home your knowledge and showcase your skills.

The shift from AI magic to engineering is vital for real-world applications. Experts discuss the collapse of the 'prompt-and-pray' era and emphasize applying engineering principles to AI features. They introduce four key architectural pillars: state orchestration, constraint generation, infrastructure reliability, and regression testing. The conversation also addresses the challenges of monolithic agents and the need for efficient output evaluation. Practical advice on networking and navigating imposter syndrome in the tech community rounds out this insightful discussion.

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