Yes. The deliverable is not the work done. Imagine you a patch submitted to your code base, you have to decide whether to start deeply reviewing it.
You are given an envelope, with a message inside revealing whether the patch came from a human contributor with expertise in the field, or whether it was prompted with "make stuff better" out of an LLM.
Do you throw the "useless" envelope away without opening it? Authorship indirectly tells us things about other work that happened, like checking alternative approaches, checking for edge-cases, and considering future work.
Comments
Yes. The deliverable is not the work done. Imagine you a patch submitted to your code base, you have to decide whether to start deeply reviewing it.
You are given an envelope, with a message inside revealing whether the patch came from a human contributor with expertise in the field, or whether it was prompted with "make stuff better" out of an LLM.
Do you throw the "useless" envelope away without opening it? Authorship indirectly tells us things about other work that happened, like checking alternative approaches, checking for edge-cases, and considering future work.
I am not saying that you hide it. I am asking is it still fair to treat it as a "slop"? slop being a derogatory term here