Episode 531: Shallow feedback and my coworker is a huge sloperator

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

<ol>
<li>
<p>Listener Jame ain’t no dance asks,!</p>

<p>Hey Space Therapists,
I am a consultant that helps big companies to fix all kind of stuff. It’s ridiculous how many different hats I wear. One day I’m the interim PM, the other day I am telling SAP devs how to use a coding agent, next day I gather stakeholder requirements for a customer self service portal. I do all of these tasks on a fairly shallow level and all of that work is happening without much coordination from my company. I think I do a good, but it’s hard gathering feedback on my work, since no colleagues are involved and I can’t simply ask the customer without revealing insecurity. Send sophisticated tips and don’t make me quit. Cheers!</p>
</li>
<li>
<p>Can I tell a coworker to stop using Claude?</p>

<p>I work on a small team at a midsized company, and a coworker keeps dropping overly verbose pull requests that are full of AI jargon. These are increasingly hard to understand, and then when I ask for design intent clarification I often get sent a long document that is even harder to understand!</p>

<p>And the code sucks! misleading docstrings, overly complicated functions, and weird places where the AI has convinced them that something needs to be backwards.</p>

<p>And often times I end up having to fix failing tests (that my coworker probably didn’t run), or report back later that their changes have degraded something in prod or is causing a lot of logging noise.</p>

<p>I worry that I’m doing the same thing and just not noticing. Code is starting to pile up in review and I don’t want to be rude and comment “ai slop” on 50% of the code! What can i do?</p>
</li>
</ol>