I used to use that clip to inspire people to laugh instead of groan while troubleshooting, and I honestly understand that for a product manager, it’s the wrong answer. But for a huge section of the population who don’t have a ground truth against which to evaluate LLM slop or where the definitions are not clear enough, I see often the only measurable thing is time and therefore it becomes the benchmark of good.
It reminds me of the Pentium 4 vs Athlon XP days counting clock speed.
I've definitely thought of that clip during my own debugging sessions.
Time is measurable, but they're measuring the wrong interval. Speed to first draft means nothing if every subsequent change takes longer because the code is unmaintainable. The technical debt from slop compounds: you're not saving time, you're borrowing it at a terrible interest rate.
In the long run, the LLM that produces less slop per request wins.