The Programming Podcast

With AI tools writing 90% of the code out there and "vibe coding" taking over our timelines, is learning the fundamentals of software engineering a waste of time? Leon and I sit down to finally answer the question we get asked every single day. We break down the truth about the "Agentic Era," why skipping the basics will break your apps in production, and how skills-based hiring is fundamentally changing what employers look for. If you are learning to code right now, or trying to land your next role, this is the exact roadmap you need to become the "AI-Augmented Engineer" that companies are desperately looking for.💡 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/I wrote a book on AI! Check it out here http://developersguide.ai/ 🔥 MAJOR ANNOUNCEMENT:Commit Your Code 2026 is officially happening! Join us September 3rd & 4th in Plano, Texas. $40 tickets, 100% goes to charity. Come for the JavaScript, AI, and startup tracks—stay for the 90-minute hands-on workshops.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 [email protected]!Danny Thompsonhttps://x.com/DThompsonDevwww.DThompsonDev.comLeon Noelhttps://x.com/leonnoelhttps://100devs.org/📧 Have questions for the show? Or are you a business that wants to talk business?Email us at [email protected]!Video Chapters0:00 - The Big Question: Do You Still Need to Learn to Code?1:00 - HUGE Announcement: Commit Your Code 2026 is Back!3:35 - The Thesis: Why AI Will Make You Ship "Bad Stuff" Faster6:05 - Is AI Really Writing 90% of the World's Code?8:13 - What Happened When a Coding Bootcamp Allowed AI9:22 - Sponsor Break: Level Up Financial Planning10:22 - The "New Edge": Why 71% of Leaders Prefer AI-Augmented Juniors12:10 - Vibe Coding, AI "Slop," and Content Generation16:22 - Vercel’s CEO on Why Fundamentals Matter More Than Ever19:34 - NACE Data: Skills-Based Hiring is Up 70% (GPA is Dead)21:19 - The Exact 6-Month Roadmap to Become an AI-Augmented Dev23:42 - Stop Guessing: How to Find the Tech Stack in Demand in Your City27:10 - The Ultimate Trap: Using AI Too Early in Your Learning Journey30:28 - What Recruiters Actually Want (Hint: It’s Not Syntax)32:33 - Real Resume Review: Why Your Bullet Points Have No Strategy36:01 - Q&A: Should You Accept a Lowball Job Offer?38:40 - Why Cold Applying is Failing You (Teaser for Next Episode)

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 [email protected]!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 [email protected]!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

For the last 18 months, we’ve been hearing that “AI is Magic.” But what happens when you connect that “magic” to your production database, your billing APIs, and your enterprise systems? It becomes a financial ticking time bomb.In this episode of The Programming Podcast, Leon and I sit down with Monica Bajaj, VP of Engineering at Okta. We are tearing down the "God Mode" tutorials you see on YouTube and talking about the terrifying engineering reality of Agentic AI.We break down the "Infinite Loop from Hell," why you need to start treating your AI like a Junior Developer with a corporate credit card, and how to actually secure your architecture before your agent bankrupts your company at 2:00 AM. If you are building with AI, deploying MCP servers, or just trying to figure out this new frontier—you cannot afford to miss this one.In this episode, we cover:- The "Financial Blast Radius" of uncontrolled AI actions- The 3 P's Framework: Purpose, Privilege, and Protection- Why standard Rate Limiting isn't enough (and why you need MCP Gateways)- Token Vaults, the "5-Minute Pulse Check," and Dynamic Zero Trust- Overcoming Imposter Syndrome when the tech world resetsMake sure to hit that like button, subscribe, and let us know in the comments: Are you giving your AI agents "God Mode"?Follow Monica Bajaj: https://www.linkedin.com/in/mobajaj/ Chapter Timestamps:0:00 - The Wake-Up Call: Why AI is Dangerous, Not Just Magic0:53 - Welcome Monica Bajaj (VP of Engineering, Okta)3:08 - The "Probabilistic Runtime" & Identity Blind Spots5:02 - Accidental Agent Sprawl & Draining Cloud Credits6:50 - The "Infinite Loop From Hell" (Bankrupting Your Company)9:24 - Financial Blast Radius vs. Text Hallucinations12:17 - The Danger of Giving AI "God Mode"14:26 - The 3 P's Framework: Purpose, Privilege, & Protection16:44 - The Biggest Anti-Pattern in Early Agent Builds18:23 - Purpose: Why Agents Need a "Job Description"20:25 - Privilege: The "Junior Dev with a Credit Card" Metaphor24:48 - Protection: Why Rate Limiting Isn't Enough (MCP Gateways)27:29 - Token Vaults & The 5-Minute Pulse Check30:32 - The SHIELD Acronym & Dynamic Zero Trust33:18 - Buy vs. Build: Identity in the Agentic Era40:03 - The 2 AM Test (If You Can't Stop It, You Can't Ship It)44:24 - Q&A: Overcoming AI Imposter Syndrome47:09 - Danny's Mic Drop: Why We Are All Imposters Right Now

In this episode, Danny and Leon break down a massive 48 hours in AI. With the surprise drop of Anthropic Opus 4.6 and OpenAI’s Codex 5.3, the landscape for software engineers has shifted again. We dive deep into what a 1-million-token context window actually means for your workflow, the rise of Agent Teams, and why "vibe coding" recently led to a massive security blunder in the dev community. We also answer a listener question about whether custom code or off-the-shelf builders like Shopify are the right choice for small business clients.📑 Chapters0:00 – Intro: The Drake vs. Kendrick of AI Drops1:20 – Opus 4.6 Metrics & Terminal Bench 2.03:02 – The 1-Million-Token Window: Game Changer or Overkill?4:36 – How Large Context Affects Codebase Scanning5:45 – Adaptive vs. Extended Thinking: Effort Parameters Explained7:50 – The Gemini Ratchet: How Google Set the Standard for Context9:15 – Playwright & MCP: Unlocking Visual Testing with Massive Windows10:55 – Understanding Context Rot & Reduction in Long Chats13:30 – Does a Million Tokens Kill RAG? (Retrieval-Augmented Generation)14:35 – Orchestration Layers: Sub-Agents vs. Agent Teams17:23 – Cost Analysis: Comparing Sonnet 4.5 vs. Opus 4.6 Pricing20:00 – Anthropic’s Response to Developer Complaints (The "Think Harder" Meme)22:20 – Skill Frameworks & Code Standards Files24:45 – The "Feel" of the Model: Speed vs. Risk-Taking in Logic27:00 – Current Dev Workflows: When to switch to Codex 5.330:50 – Prompt Engineering in the Thinking Model Era32:45 – Sam Altman’s "Bar" & The Reality of Benchmarks36:15 – Is Coding Dead? Addressing the Hype Cycle and Management Fears37:55 – The "Maltbot" Security Blunder: Why Humans Must Stay in the Loop42:15 – AI in WebDev vs. Embedded Systems & Cloud45:55 – Q&A: Website Builders (Shopify/Wix) vs. Custom Code for Clients50:50 – Final Thoughts: Selling Your Time and Knowledge, Not Just Syntax

This isn't about a new JavaScript framework; it's about a significant shift in software engineering. If you're in tech or aspire to be a software developer, this discussion is crucial for understanding the future of web development. ✅ If you made it to the end, comment: “Claude Code!” so we know who is a real one!In this episode, Leon and I live-react to the viral tweet from Andrej Karpathy (founding member of OpenAI, former Tesla AI Director) that has the entire dev world talking. Karpathy reveals that his workflow has shifted from 80% manual to 80% agentic in just one month. We’re diving deep into what it actually means to "program in English" and whether our skills are atrophying as AI takes the wheel.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 [email protected]!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 [email protected]!We also discuss:- The "Vibe Coding" Shift: Why the "Idea Guy" is dead and why the "Builder" is winning.- Atrophy vs. Expansion: Are we losing our edge, or just building faster?- The "Slop-ocalypse": Preparing for 2026 as GitHub gets flooded with AI-generated spaghetti code.- Real-world Impact: How I’m using these exact agentic workflows to build EventConvo.Special Guest Mention: Shout out to Logan Kilpatrick from the Google Gemini team for the insights that sparked this conversation.Chapters0:00 – The Biggest Change to Coding in 20 Years1:05 – Shoutout to Logan Kilpatrick & Gemini1:52 – Reacting to Andrej Karpathy’s Viral Tweet 2:40 – "I am Programming in English Now" 4:05 – How Our Prompting Has Evolved (Whisper Flow & Opus) 5:30 – Does Agentic Coding Feel "Wrong"? 6:55 – The Theo T3 "Toothbrush" Workflow 7:45 – Building EventConvo: AI as a Force Multiplier 9:15 – Is AI Taking Developer Jobs? (The Stack Overflow Comparison) 12:35 – The Death of the "Idea Guy" 14:15 – Why You Still Need an IDE (Watching Agents Like a Hawk) 18:30 – The Senior Dev Gap: Pattern Recognition vs. Logic 20:20 – The Fear of Skill Atrophy 23:10 – Speed Ups vs. Expansion: Are We Doing Too Much? 27:40 – Leverage: Stop Telling AI What to Do 32:10 – Is Coding Still Fun? 35:50 – 2026: The Year of the "Slop-ocalypse" 43:05 – What Happens to the 10x Engineer? 48:20 – Future Tech: Anthropic Co-work & Gemini CLI 52:45 – Ask Danny & Leon: How to Crush a 3-Hour Virtual Onsite 59:20 – Final Thoughts: Now is the Time to Play

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 [email protected]!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 [email protected]!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

Is Tailwind actually “dying” or are we watching something bigger happen in real time?In this episode of The Programming Podcast, we dig into a brutal 2026 reality check for developers: the tools and communities we’ve relied on for years are getting shaken up by AI in ways most people didn’t see coming.We break down the Tailwind situation, including the GitHub discussion that surfaced a behind-the-curtain truth about modern open source: documentation traffic is the funnel, and AI is bypassing it. When LLMs stop sending humans to your docs, what happens to paid products, sponsorships, and ultimately the ability to maintain the framework at all?Then we shift to the other major signal: Stack Overflow’s decline. The charts are ugly, and the reasons are deeper than just “people use AI now.” We talk about the human cost of hostile community dynamics, why developer Q&A moved to Discord long before LLMs took off, and what it means when the internet’s most “verified” coding resource starts fading.Finally, we go big-picture: if open source loses funding and loses maintainers, what happens to the future of software? And where do new developers go when both the old learning paths and the new AI-heavy paths are unreliable?✅ 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 [email protected]!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 [email protected]!Subscribe if you want honest, no-hype conversations about where software development is heading in 2026.

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 [email protected]!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 [email protected]!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

The “prompt-and-pray” era is over — and that’s a good thing.In this episode, we break down why AI “magic” collapses under real production traffic (edge cases, hallucinations, messy inputs, and even infrastructure-level failures)… and what replaces it: actual AI engineering.Danny frames the shift with four architectural pillars that make LLM features shippable and reliable:- State orchestration (stop treating models like employees — they’re stateless CPUs)- Constraint generation (JSON forcing, schema-driven outputs, type-safe sampling)- Infrastructure reliability (retries, backoff, fallbacks — because inference can and will fail)- Regression testing & evals (measure prompts like code, break builds when quality drops)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 [email protected]!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 [email protected]!We also hit the reality of agent “throughput” vs human review bottlenecks (Phoenix Project vibes), why monolithic agents are a trap, and a listener question about networking + credibility after pitching an MVP that isn’t fully shipped yet.If you’re building AI features for real users — not demos — this is the blueprint.00:00 — The “prompt-and-pray” era is over02:49 — AI hype fades: guardrails + reality06:34 — Deterministic software vs probabilistic models07:29 — The 4 pillars of AI engineering (overview)11:37 — Pillar 1: state orchestration (FSM, stateless models)20:26 — Pillar 2: constraint generation (JSON, schemas, type safety)28:28 — Pillar 3: infra reliability (retries, fallbacks, failures)32:21 — Pillar 4: evals + regression testing (LLM-as-judge)43:40 — Listener question: networking, MVP pressure, and credibility

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 [email protected]!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 [email protected]!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