My assumption was that AI-generated code would make reviews easier because criticism of the code wouldn't feel like criticism of the author.
Instead, I've repeatedly seen people strongly defend AI generated code, and sometimes even defend AI explanations that are demonstrably incorrect.
Is anyone else seeing this?
If so, what do you think is driving it? How are you handling it within your team?
Also, has anyone found effective ways to reduce the influence of "leading question" prompts?
I very much want to keep human in the loop style paradigm within our teams, but at the same time I do wonder if my life would get a whole lot easier if instead we jumped on the "loop/factory/vibe" train.
My assumption is the push back comes when the expectation is if the AI made code was bad, that means the person who submitted it missed something. So they got “caught” being lazy and don’t want to admit it.
> I very much want to keep human in the loop style paradigm within our teams, but at the same time I do wonder if my life would get a whole lot easier if instead we jumped on the "loop/factory/vibe" train.
I would imagine it gets easier, until it doesn’t. To jump on that train you need to be fully ready to not care, good or bad.
Several years ago my managers wanted me to move up into a management role. I gave it a shot, but hated it. I went back to an IC role and decided to stop caring so much, to avoid being put in that position repeatedly. Let the managers do their thing, and if things are a mess, then things are a mess. I didn’t quite grasp the level of apathy some people have. I’ve found it much more stressful to sit back than to engage and try and fix everything. I feel like handing the wheel over to AI would go much the same way.
Juniors are doomed, nobody is writing anything ever again by hand.
As you've stated, years of development has made me expect a certain level of discourse as people will inevitably want to defend the quality if they think it's reasonable.
Maybe my post is a form of AI psychosis in itself....