How are y'all handling coworkers who post slop?
-
How are y'all handling coworkers who post slop?
Several of our contractors have made rather voluminous wiki pages that are heavily redundant and over-explanatory. So far my approach has been to just... quietly not read them, and pretend the pages don't exist. (If I need information that the page is supposed to have, I just ask the contractor to explain in Slack or a meeting.) It's bad for the company in a bunch of different ways, but the company is all-in on AI and doesn't want to hear dissent, so there's no way to address this systemically. (And I'm not invested in the company's long-term health.)
One coworker posts AI outputs sometimes, but is a bit more discerning, and we have a good enough relationship that I've been able to explain that hey, I'm not reading that, but you're free to tell me anything you learned *after* you verify it.
I'm curious to hear how others are handling it.
-
How are y'all handling coworkers who post slop?
Several of our contractors have made rather voluminous wiki pages that are heavily redundant and over-explanatory. So far my approach has been to just... quietly not read them, and pretend the pages don't exist. (If I need information that the page is supposed to have, I just ask the contractor to explain in Slack or a meeting.) It's bad for the company in a bunch of different ways, but the company is all-in on AI and doesn't want to hear dissent, so there's no way to address this systemically. (And I'm not invested in the company's long-term health.)
One coworker posts AI outputs sometimes, but is a bit more discerning, and we have a good enough relationship that I've been able to explain that hey, I'm not reading that, but you're free to tell me anything you learned *after* you verify it.
I'm curious to hear how others are handling it.
@varx I ask them to walk me through it. In detail.
-
@varx I ask them to walk me through it. In detail.
@afeinman That would be for code though, right? I was thinking more of chat messages, wiki docs, etc.
-
@afeinman That would be for code though, right? I was thinking more of chat messages, wiki docs, etc.
@varx No, both. Had someone show me an invented work plan he hadn't bothered to review before people took it as normative; that was "exciting".
-
How are y'all handling coworkers who post slop?
Several of our contractors have made rather voluminous wiki pages that are heavily redundant and over-explanatory. So far my approach has been to just... quietly not read them, and pretend the pages don't exist. (If I need information that the page is supposed to have, I just ask the contractor to explain in Slack or a meeting.) It's bad for the company in a bunch of different ways, but the company is all-in on AI and doesn't want to hear dissent, so there's no way to address this systemically. (And I'm not invested in the company's long-term health.)
One coworker posts AI outputs sometimes, but is a bit more discerning, and we have a good enough relationship that I've been able to explain that hey, I'm not reading that, but you're free to tell me anything you learned *after* you verify it.
I'm curious to hear how others are handling it.
@varx I have basically the same strategy. Except I also occasionally add the :old-man-yells-at-claude: emoji below such a thing (esp. if coming from someone higher up).
-
R relay@relay.infosec.exchange shared this topic
