[t-writescode]

That sounds like a fantastic way for a malicious actor or an unintentional prompt injection exploit to sneak into a codebase.

Perhaps you could explain how this is different from rubber stamping, if it’s just 30 seconds of reading.

Does the conversation you have reveal what they actually want?

And what about the 2000 line change? Does that get stamped after someone talks about the change but without deeply reading it?

[SpicyLemonZest]

Typically what happens is that we have a good conversation, we make progress towards figuring out what they should want to do and how they should try to do it, and the 2000 line PR or 10 page doc gets abandoned. I do read things in detail when I expect I might one day be convinced to approve them, but that fraction has plummeted from 95% to like 20% since January.

[t-writescode]

Have you noticed an increase in their willingness to “do the right thing first time” during these last 6 months since your approval rate has dropped that much? (Even if the right thing is to have more conversations)?

Do you know if there’s a way to incentivize them to lean toward doing the right thing first? Are the company and stakeholder goals and objectives in line with them making progress toward higher quality engineering? That is, are these juniors protected from randoms asking them to circumvent good process, etc?

[SpicyLemonZest]

Unfortunately, I've had a number of people explicitly defend that nothing's going wrong here. Their view is that, if sloppy code is cheap, everyone might as well produce some to illustrate their ideas before having a conversation. I'm skeptical of that position but haven't had much luck in fighting it.

> Are the company and stakeholder goals and objectives in line with them making progress toward higher quality engineering? That is, are these juniors protected from randoms asking them to circumvent good process, etc?

In my personal experience yes, but I've seen a few teams and heard stories of many more where the juniors are not protected and they just ship regressions and outages all the time now. I think the trend towards AI cost controls will mitigate this, although the impact will of course be uneven as companies behind the curve discover powerful agentic coding for the first time.

[nozzlegear]

You're fighting the good fight.