Yeah - I wish my team would adopt a "no AI prose" rule for team communication.
It's one thing to say "please review this code that I used AI to generate". It's entirely different to say "Please read this 7 page document that AI generated about a plan to generate this code, and I'm passing it off to you as my plan"
It puts the onus of understanding onto the reader (writing a wall of text used to put the onus of understanding on the writer), and if the prompter hasn't read the output, then it's putting most of that effort onto the reader.
Horrible in practice, and yes - I can tell every single time someone dumps an AI generated message into the chat, because it's not succinct, it rarely directly answers my question, it's overly verbose, it has no style, and it lacks the depth of understanding of how our team works together.
It's one thing to say "please review this code that I used AI to generate". It's entirely different to say "Please read this 7 page document that AI generated about a plan to generate this code, and I'm passing it off to you as my plan"
It puts the onus of understanding onto the reader (writing a wall of text used to put the onus of understanding on the writer), and if the prompter hasn't read the output, then it's putting most of that effort onto the reader.
Horrible in practice, and yes - I can tell every single time someone dumps an AI generated message into the chat, because it's not succinct, it rarely directly answers my question, it's overly verbose, it has no style, and it lacks the depth of understanding of how our team works together.