plumbees
Joined 1 year ago
Joined 1 year ago
As I wrote this i switch to the phrase communication-style because I realize that when he does his code review it's literally just a quick pass and a paste, but unfortunately when I do AI code reviews I review every single review item and push back individually on each item, research the items, write tests against what the review says and basically curate the code review I give out, which takes me 3 hours and then I have a boss angrily messaging me asking why the code review isn't done.
So on the one end I've managed to reduce toxicity in the reviews, but the tradeoff is toxicity in the expectation of a rubber stamp.
+ Priorities shift dramatically. I see director level people running around like chickens without heads trying to fill in an excel sheet because one of the higher ups has sent down a directive; without them realizing that the time spent doing so is meaningless dribble that doesn't matter. It's like things that were not obvious time sinks are now very obvious and I'm less patient (of nonsense) because I have something more important to care about.
yeah at some point my job was: "I create complicated PDFs for clients that want them but will never read them."
Not more efficient at handling this but more able to handling things at a lesser quality at scale.