Episode 446: Wading through AI slop and they don't get git

<p>In this episode, Dave and Jamison answer these questions:</p>

<ol>
<li>
<p>A listener named Matthias (mah-TEA-as) asks,</p>

<p>In episode 444 you’re talking about the problems when hiring in the age of AI. I’m a manager who’s trying to hire right now and frankly I’m at a loss. If feels like I’m wading through a sea of AI slop. What tips do you have to cut through the slop and reach actually good candidates?</p>
</li>
<li>
<p>Where I work the developers do not seem to “get” source code control systems like git. I’m not a developer but have worked with developers at previous jobs and usually the developers instituted good source control practices themselves.</p>

<p>Our developers know they should push their code to the repo but only do it weekly/monthly, treating it as a “backup”. Some back up their laptops using tools like Time Machine so think have taken care of safeguarding their source code that way.</p>

<p>How can I convince them that working in git, committing their code as they go, pushing regularly, branching/merging, tying code updates to tickets, etc will benefit them far more in the long run?</p>
</li>
</ol>