Should you read the code, is RAG dead, and did Skills kill MCP?
Source
GPS
Author
GPS
Date
Key takeaways · AI-distilled
GitHub's podcast hosts push back on 'you don't need to read AI-generated code': the reviewer is still accountable, so review depth should match risk (a production auth refactor vs. a CSS tweak), not treat every AI-generated change identically.
On AI and hiring, the argument is that companies increasingly ask candidates how they use AI, but the stronger signal is judgment: being able to explain when to use AI, when to work manually, and how you review generated code, not blanket adoption or refusal.
Skills didn't kill MCP: MCP standardizes how agents connect to tools and data, while Skills package process and context windowThe maximum amount of text a model can consider at once — its working memory for the current conversation or task.Full definition → knowledge (often in readable Markdown) — the piece argues they solve different problems and compose together rather than compete.
RAG isn't dead, just less discussed: without good retrieval, models either rely on stale training data or spend extra tokens searching for context; groundingTying a model's answers to checkable sources — retrieved documents, live data, tool results — instead of letting it answer from memory alone.Full definition → retrieval narrows the search space and combines with agents, skills, and MCP in the same workflow.
On 'if you need to fine-tuningTaking a trained model and training it a bit more on your own examples so it gets better at one specific job.Full definition →, your code is bad': modern models have seen enough common patterns that struggling to parse a codebase is itself a maintainability signal — code confusing to a model is likely confusing to a new human teammate too.
Terms in this piece · Glossary
AI agent — An AI system that doesn't just answer once but works toward a goal in a loop — taking actions, reading the results, and deciding what to do next.
fine-tuning — Taking a trained model and training it a bit more on your own examples so it gets better at one specific job.
context window — The maximum amount of text a model can consider at once — its working memory for the current conversation or task.
grounding — Tying a model's answers to checkable sources — retrieved documents, live data, tool results — instead of letting it answer from memory alone.
Why it matters
GitHub's podcast argues you still must review AI-generated code but calibrate depth to risk, and works through the RAG-vs-fine-tuning and Skills-vs-MCP debates with concrete reasoning instead of slogans.
