3 ms·
The inverse of this is "AI Loopidity" where we burn cycles inflating then deflating information (in emails, say, or in AI code that blows up then gets reduced o
by tomrod 1y ago
The inverse of this is "AI Loopidity" where we burn cycles inflating then deflating information (in emails, say, or in AI code that blows up then gets reduced or summarized). This often also leads to weird comms outcomes, like saving a jpg at 85% a dozen times.
- nicbou 1y agoAn early article about LLMs called it "a blurry jpeg of the web" for exactly those reasons. It's a good read.
- wood_spirit 1y agoAnd each cycle introducing error like a game of telephone
- tomrod 1y agoAnd with no governance in place (like an engine governor) you get cascade failure.