One early example I heard about slop code being bad was that if you have a process that is repeated, an LLM will not write a function that is broadly scoped so it can handle a significant number of related use cases, it will write different code for each instance, so when that process fails you have no idea which version is responsible. Seems like the kind of thing QA would flag.
One early example I heard about slop code being bad was that if you have a process that is repeated, an LLM will not write a function that is broadly scoped so it can handle a significant number of related use cases, it will write different code for each instance, so when that process fails you have no idea which version is responsible. Seems like the kind of thing QA would flag.