Ever watch a newcomer to programming write code? Too often, they're programming by auto-correct. They type a plausible-sounding function name, look at the fuzzy-find hovertext that pops up, pick something plausible, and see if it works. Rinse, repeat. A valid approach for a beginner, but let us not pretend that, at least at this stage, the coder actually *understands* what they're doing.

They're lab rats, poking the button until treats come out.

Thanks to the Anthropic code disclosure, we now know LLMs do exactly the same thing, only much faster.

This is not productivity. This is not engineering. This is, to coin a phrase, "Guessing at scale."

@ewhac Code is not an asset; code is a liability. Being able to spew out code faster means that you gain liabilities at an increased rate.

I recently heard someone refer to the process of writing code as "enbugging".