Custom MCPs, Dropped Databases, and the Junior Dev Pipeline

Top-Line Summary

A cautionary tale about a developer who let Claude Code run Terraform with admin credentials — and lost their production database, snapshots, and load balancers — sets the tone for an episode about what happens when you skip guardrails. Brett and Travers connect it to the broader question of whether AI tools are structurally collapsing the junior developer pipeline, and why shipping bad AI-generated code is a process failure, not a technology problem.

Show Video

The “Pre-Show” Context

This is actually the third recording attempt for this episode — the first two were killed by disk space issues on Brett’s Mac. Brett jokes that he needs his own process checklist for live streaming, and Travers agrees they’ll be in the same boat next week without one.

The Engineering Rundown

• Supercharge your IDE: Custom .NET MCP servers for Amazon Q Developer (00:00)

  Brett and Travers open with custom MCP servers, noting they’ve both built their own personalized setups. The article focuses on .NET MCP servers for Amazon Q Developer, but Brett’s main reaction is confusion about AWS’s naming: Q, Q for Business, Q Developer, Kiro — at this point, what’s the difference? Travers reads Q Developer as the IDE extension for interacting with your AWS environment, and thinks Kiro can hook into it. Neither is fully sure, and they agree the branding is a mess.

• AWS Load Balancer Controller adds GA support for Kubernetes Gateway API (02:30)

  Brett’s note was “you lost me at Kubernetes,” but Travers explains why this matters for large multi-tenant organizations. It’s a change in the Kubernetes spec enabling a general gateway layer with internal routing, solving ALB rule and target group limits — roughly 100 target groups per ALB. If you’re not running thousands of services across tenants, this isn’t for you.

• Database Savings Plans now support OpenSearch Service and Amazon Neptune (04:00)

  Savings plans now cover additional database types including OpenSearch and Neptune. Straightforward: if you’re running predictable database workloads, commit and save. Databases are the foundation of most apps and they run 24/7, so this is an easy win.

• AWS Simplifies IAM role creation and setup in service workflows (05:00)

  You can now create service roles for EC2, RDS, and other services directly from their consoles without navigating to the IAM console first. Travers calls it a quality-of-life improvement for console users. Brett admits he still uses the console for exploration — figure it out by clicking, then codify it later. Currently supports only a small subset of services.

• Amazon GameLift Servers launch DDoS Protection (06:45)

  AWS added a free DDoS protection layer to GameLift — no additional charge. Travers explains this is essentially Shield for UDP traffic. Game servers use UDP, and DDoS via UDP floods is a massive problem for multiplayer games. Companies used to spin up huge proxy fleets of EC2 instances to filter that traffic. Classic AWS value prop: focus on building games, offload the infrastructure protection. Brett pivots into a Battlefield 6 rant — launched at 750K players on Steam, now averaging about 40K.

• Amazon Bedrock AgentCore Runtime now supports stateful MCP server features (09:15)

  Each agent session runs in an isolated micro VM with its own resources, using session IDs for continuity. If a session ends, the VM can hibernate and resume later without starting from scratch. Travers calls it “Lambda for your agent sessions” — spin up an image on demand, keep it warm, let it go cold. Ties into the isolation themes they’ve discussed in recent episodes.

• OpenBrain Update — Memory System Working, Retrieval Challenges (12:00)

  Brett’s personal knowledge base is operational — Claude built everything, no hand-written code. He’s using GitLab issues as a task queue: store up issues, point Claude at them, let it prioritize and execute. The MCP integration retrieves memories well, but the Slack integration is falling on its face — same underlying functions, different results. Brett subscribed to Claude Max after burning through credits running three terminals simultaneously. He stumbled into a sub-agent research flow for the first time, where Claude fired off a background research agent that ran for about 30 minutes and came back with a phased approach broken into issues. The distinction between “back and forth hoping to get lucky” and “go do research and return with options” was a turning point.

• Kiro for Spec-Driven Development — Personal Kanban Project (21:30)

  Brett is building a personal Kanban board to replace Jira, which is overkill for his needs. Early impressions of Kiro: out of all the tools he’s used, it does the best job at teasing out ideas from an initial prompt. Three to four rounds of clarifying questions before writing any code — desired outcomes, edge cases, possible future features. No code yet, but the spec process has been impressive. Travers notes this aligns with Amazon’s stated goal for Kiro as a spec-driven development tool, and the newer Claude models in plan mode show similar behavior.

• How I Dropped Our Production Database and Now Pay 10% More for AWS (29:00)

  The episode’s cautionary tale. A developer gave Claude Code Terraform access with admin credentials and wiped their production database, load balancers, bastion hosts, and snapshots — two and a half years of data, nearly 2 million rows. AWS Support restored it using internal tools. Brett notes Claude’s recommendation was sound (separate VPC), but the author overruled it to save a few bucks. He’d have gone further — separate AWS account entirely. The bigger question: unless this was running in YOLO mode, Claude Code should have prompted before running destructive commands. Brett takes a shot at Terraform’s state management and says this is one reason he prefers the “slower” CloudFormation. Deletion protection, environment separation, and backup hygiene are the non-negotiable takeaways.

• Perhaps not Boring Technology after all — Simon Willison (39:15)

  The fear that AI coding tools would lock everyone into React and Python hasn’t materialized — as models get smarter, they handle less mainstream stacks just fine. Brett experienced this firsthand: Claude Code dug through GitHub issues and source code for a CIDC-CMD tool (Kudos dashboard management), reading other people’s bug reports and deducing solutions for his specific problem. Stack Overflow is probably dead. Dev.to just sold. AWS re:Post — why go there when the knowledge is in the training set?

• Should I be a carpenter? — Casey Muratori and Dmitri Spanos (44:00)

  Brett only got halfway through this video but it resonated. The core worry: if you hollow out the junior-to-senior developer pipeline by replacing juniors with AI subscriptions, what happens to the industry in 10-20 years? Brett’s pessimist take: for a lot of companies, it’s just math — $100/month for Claude Max versus $80K/year for a junior dev. Travers notes the current glut of engineers from over-hiring complicates the picture, and supply-and-demand will eventually rebalance. Neither has a clean answer.

• AI should help us produce better code — Simon Willison (50:30)

  If you’re shipping worse code with AI tools, that’s a choice you’re making. You don’t have to ship what gets generated — evaluate PRs, throw away bad output, try again. Brett connects this to the production database story: process exists for a reason. Change boards, staging environments, CI pipelines, PR reviews — all emerged because someone had a terrible day without them. The human-in-the-loop responsibility doesn’t disappear because an agent wrote the code.

Off-the-Clock Recommendations

• The Conjuring series (2013–2021) — Travers is working through the franchise with Patrick Wilson and Vera Farmiga. The third one is basically a legal drama involving demonic possession and a murder trial. Connected to The Nun films.
• Watchmen (2009) — Brett wants to rewatch it after remembering Patrick Wilson as Night Owl with the ship hidden in the subway.
• Stellaris (Paradox Interactive) — Brett and his friend Frank dusted off this space 4X game after a year away. So many patches it felt brand new. Paradox now offers a $10/month subscription for all ~60 DLCs. Brett calls the soundtrack one of the best in space gaming.