You can just say it: the best definition of AI slop

Re:You can just say it: the best definition of AI slop by patates on Saturday May 30, 2026 @05:19AM (#48334285)

Usually my back and forth with the llm is much longer than the result. Add the skills, the context, access to my calendar... I'd probably need to send a zip file instead of 1 short paragraph of text. Maybe letting agents representing people, with access to non public information will be secure in the future. For now, that part is manual. I need to control information on the way out.

You probably should find it insulting when someone obviously didn't take the time needed to form a proper response. Prompting "write something apologetic and kind for not attending their wedding" and sending the response is not okay. Like this example, it's easy to recognize when being a human counts, we should also be able to justify automating stuff when it really is just boring information exchange.

[ Parent | on HN ]

Re:You can just say it: the best definition of AI slop by blks on Saturday May 30, 2026 @05:54AM (#48334497)

Do you really need the agents, skills and them having access to your calendar, plus multiple back and forth, to create an email about scheduling something - and anyway you will have to check it manually?

[ Parent | on HN ]

Re:You can just say it: the best definition of AI slop by patates on Tuesday June 02, 2026 @01:31AM (#48366438)

Yes because it's not a single calendar, and I sometimes need to be reminded of potential plans (not saved on a calendar), history with that specific person ("oh I already made a demo to this person 2 years ago and from my notes, it seems that I didn't get a lot of feedback, perhaps prioritize someone else?"), and other context. I offer the LLM context, and I in return get a distilled context from which it's easier to make decisions.

Writing important emails used to be a 1-2 hour occasion, nowadays only 15 minutes, but surely not 10 seconds.

[ Parent | on HN ]