677: Background Code Agents, Append AI, and RSS Starter Packs

What It Covers

Chris and Dave explore background coding agents in VS Code Copilot, discuss practical AI implementation challenges versus hype, evaluate Model Context Protocol adoption barriers, and propose an RSS starter pack for developers seeking curated content.

Key Questions Answered

• •AI Agent Reality Check: Background coding agents excel at routine tasks like adding server headers or writing tests but require human oversight to prevent architectural mistakes. One developer's AI solution worked perfectly but missed an obvious optimization that would have eliminated duplicate code paths entirely, revealing agents optimize for instructions given rather than best solutions.
• •Productivity Perception Gap: Studies show developers feel 20% faster using AI but measure 20% slower in reality. The technology excels at getting developers unstuck and moving code forward into their domain expertise, but creates false confidence where juniors appear more competent than actual skill level, potentially eliminating apprenticeship opportunities and human teaching moments.
• •MCP Adoption Barrier: Model Context Protocol provides standardized APIs for AI tools and actions, but lacks real-world usage stories beyond five-minute demos. Developers need concrete examples of daily MCP workflows that deliver measurable value rather than proof-of-concept Figma imports, highlighting the gap between technical capability and practical implementation in production environments.
• •RSS Curation Problem: RSS readers fail new users when high-volume sources like The Verge publish hundreds of posts daily, drowning out smaller blogs. Successful RSS usage requires manual curation work over time, suggesting starter packs with 15-20 lower-volume feeds from thoughtful bloggers like Jeremy Keith's Links feed, Jim Nielsen, and Maggie Appleton provide better onboarding than OPML dumps.
• •Corporate AI Mandates: Companies increasingly require teams to prove maximum AI value extraction before approving new headcount, forcing developers into mandatory usage regardless of effectiveness. This creates unequal workload distribution where junior developers generate AI code in minutes while senior developers spend hours reviewing detailed commits, inverting traditional mentorship dynamics and potentially degrading code quality.