Unfortunately people are being encouraged to use LLM in docs, emails, and presentations so it's probably a losing battle.
I think if you work somewhere that this is the result, you're unlikely to have much progress challenging anything directly. In order to actually have change you need to be able to challenge and stamp out these sorts of behaviours.
"Do not make negative assumptions" basically. But also a drop in how often and quickly I did reviews.
I've been guilty of acting as a middleman for review comments from difficult coworkers. I farm out my interaction to avoid the confrontation, mental exhaustion, and to avoid negative feelings I got from those reviews. I don't mean 'my work is being challenged', I mean people who: delay, nitpick, blow up architecture after not participating in design, assert false info as truth and require you prove them wrong, require 10x evidence of everyone else. Not people who are like 'Hey, I don't understand this code can you add some comments or lets hop in a room for review'
I've also been on the receiving end. I like to think I'm NOT one of these toxic reviewers.
Now, we have Business Owners and Managers who are now even further away from engineers. Important meetings have 0 engineers in them ( a couple people who think they're engineers because they were for 5 years in the 80s ). Output is an AI generated transcript that gets copy/pasted into copilot to generate jira tasks by the Product Owner.
It seems like we (humans) really don't like working with other people. Or, maybe we like working with people who can advance our careers and want to automate interaction with people who cant?
I think this effort by Business Owners to set up an AI wall may be the closest I've seen to 'digital classism' (maybe there is a better term for it?).
https://croissanthology.com/earring
We like whispering earrings. We'll follow a low friction happy path even if it leads us off a cliff.
No. We hated that too.
Actual research is, of course, fine.
My experience has typically been that engineers respond, "Claude said..." and then say what they think about it. If people are really receiving just a straight dump of AI response from their colleagues, then yeah, I would be disappointed too.
But, I have no problem receiving from a colleague, "Claude says ..., but I don't know what to make of it." The embedded space can be really hard, so I don't fault someone for feeling clueless about something. I feel that way every time I get handed something new to work on which I have zero experience with.
I don't presume that someone will have an answer I'm looking for. I'm pleased when they do, but often I just get breadcrumbs, and I have to solve the puzzle for myself.
I ask him 4G LTE/5G NR questions all the time. I don't know ahead of time if he'll know the answer, but (1) it'd be a solid bet that he does and (2) it's his responsibility to know it given his role.