<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Mentorship on NoRaincheck</title><link>https://noraincheck.github.io/tags/mentorship/</link><description>Recent content in Mentorship on NoRaincheck</description><generator>Hugo</generator><language>en-US</language><copyright>NoRaincheck</copyright><lastBuildDate>Sat, 07 Nov 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://noraincheck.github.io/tags/mentorship/index.xml" rel="self" type="application/rss+xml"/><item><title>Teaching Juniors in the Age of LLMs</title><link>https://noraincheck.github.io/posts/teaching-juniors-in-age-of-llm/</link><pubDate>Sat, 07 Nov 2026 00:00:00 +0000</pubDate><guid>https://noraincheck.github.io/posts/teaching-juniors-in-age-of-llm/</guid><description>&lt;p&gt;Coding agents are inevitable. It would be highly unusual, and maybe even a red flag, if a technical role did not have AI available at this stage.&lt;/p&gt;&#10;&lt;p&gt;What does this mean for juniors? How do we bring up juniors in the age of AI?&lt;/p&gt;&#10;&lt;p&gt;These are questions I&amp;rsquo;ve had to tackle in the last 2 weeks, and here are my broad thoughts.&lt;/p&gt;&#10;&lt;h2 id="focus-on-prototyping-first"&gt;Focus on prototyping first&lt;/h2&gt;&#10;&lt;p&gt;The important thing is to let them get familiar with coding agents and prototype changes. They should be comfortable screwing around with a project in a development environment, breaking it, testing it, and debugging UX changes.&lt;/p&gt;</description></item></channel></rss>