The biggest dilemma I face at work these days is how to politely say "ay yo, this is AI slop!"

[carnage4life@mas.to]

The biggest dilemma I face at work these days is how to politely say "ay yo, this is AI slop!"

Suggestions welcome.

[ambiguous0@mastodon.social]

@carnage4life our sales people have embraced llm generated sows which promise things we can't deliver, estimate efforts and costs that cannot be attained. It's horrible stuff, but as I write this, not much different than what they were doing before really...

[peterbroks@mastodon.social]

@carnage4life Hello, is there anybody there?

[graham_knapp@hachyderm.io]

@carnage4life how about something like "what prompt did you use to generate this? I think we may need to start again from there..."

[discobeez@mas.to]

@carnage4life "Did you review this before sending it?"

[spdrnl@sigmoid.social]

@carnage4life Ask: "Can you take me through the steps you took to come to this conclusion or idea?"

This discussion should convey critical thinking. Typical this discussion leads to nowhere.

[ukeleleeric@mstdn.social]

@carnage4life Have you thought at all about this idea, or just proved that you're not worth what you're paid by getting a machine to do it?

[bentsai@social.lol]

@carnage4life my way to cut through the crap is to ask “why?” Why did they make this or that decision. If pushes them to be accountable for whatever artifact they are presenting.

[ambihelical@hachyderm.io]

@carnage4life smells a bit clanky

[shadowferret@the9thcircle.club]

@kagihq@mastodon.social @countablenewt@mastodon.social ​​

[fibrojedi@gamepad.club]

@countablenewt @kagihq Stick with the original - it is more efficient, uses fewer brain resources and staff time, and is likely to be taken as a call to change, rather than a mild telling off.