I think it’s more useful to look at the tasks models haven’t gotten better at over time, and the tasks that are hard for them get better at in principle. The two best examples of these are:
- Deep familiarity with the codebase
- Technical communication
I think it’s more useful to look at the tasks models haven’t gotten better at over time, and the tasks that are hard for them get better at in principle. The two best examples of these are:
- Deep familiarity with the codebase
- Technical communication
Al studies that demonstrate the lack of use, and actually the negative impact of slop machines for coding are also delusional I guess.
Not delusional at all. I’d rather phrase them as describing an ill-fitting or maladapted usecase or use method. Strange how Capitalism keeps demanding we use those.
Maybe we should look into that. Or like… Ask ourselves how to hose the Capitalism off of the sometimes-useful number-cruncher. Or what literacy looks like with this tool, instead of asking it to think for us.
What are you talking about? A study showing that code made with the “help” of slop machines is worse in quality and contains more issues is unrelated to capitalism.
If anything, people defending slop coding are the ones brainwashed by capitalism, with a cult of the “faster/more efficient” that makes them believe that code produced fast is good code no matter what.
Hallucinatory slop has no place in the making of software, or anything else.
You saying “slop machine” makes you sound so smart!