<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Developer Education on No Semicolons</title><link>https://nosemicolons.com/tags/developer-education/</link><description>Recent content in Developer Education on No Semicolons</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 27 May 2026 11:32:14 +0000</lastBuildDate><atom:link href="https://nosemicolons.com/tags/developer-education/index.xml" rel="self" type="application/rss+xml"/><item><title>The AI Code Generation Onboarding Gap: How to Train New Developers on AI-First Teams</title><link>https://nosemicolons.com/posts/ai-code-generation-onboarding-gap-training-new-developers/</link><pubDate>Wed, 27 May 2026 11:32:14 +0000</pubDate><guid>https://nosemicolons.com/posts/ai-code-generation-onboarding-gap-training-new-developers/</guid><description>&lt;p>Picture this: You&amp;rsquo;ve just hired an incredible senior developer with 10+ years of experience. They&amp;rsquo;ve shipped features at scale, mentored junior devs, and can debug gnarly production issues in their sleep. But when they join your AI-first team and see developers pair-programming with Claude or having GitHub Copilot write entire functions, they look like they&amp;rsquo;ve stepped into an alternate universe.&lt;/p>
&lt;p>Sound familiar? You&amp;rsquo;re not alone. As more teams adopt AI-first development workflows, we&amp;rsquo;re discovering a fascinating challenge: some of our most experienced developers struggle the most with this transition. It&amp;rsquo;s not about intelligence or adaptability—it&amp;rsquo;s about unlearning decades of muscle memory and embracing an entirely different relationship with code.&lt;/p></description></item></channel></rss>