Brilliant essay -- "The Copilot Delusion" -- on how "AI" is ruining so much, programming in this case.

https://deplet.ing/the-copilot-delusion/

"We’re building a world where that curiosity gets lobotomized at the door."

@dangillmor
I'm no coder but I appreciate how good the writing is. At least half a dozen brilliant metaphors and characterisations. Joy to read.
@dangillmor That is a brilliant essay.
As a non-coder I made a very abstract comment about enshittification of the already bloated software which now is the standard after a talk from a certain professor. She wasn't amused about me saying that software would evolve in everything being dumb the same way and that there at a certain time won't be anyone who understands code and who can clear up the mess.

@dangillmor I couldn't have said it better myself:

"Write a library. Invent a macro. Reclaim some dignity."

@dangillmor That was a good essay. Yeah, the stuff that AI puts out is mediocre at best, and even then it was only able to produce it because of the clever coders that wrote it to begin with.
@dangillmor Generative AI is “…autocomplete with a superiority complex”.

@dangillmor "My boss corners me. 'Why aren’t you pairing more with him? He types twice as fast as you.' Of course he does. So does a cat having a seizure on a mechanical keyboard."

haha

@cocoaphony @mbroome seen this yet?
@llorenzin @cocoaphony
Yes! Very much enjoyed it.
This truth resonated with me:
"AI isn’t helping you build something novel. It can’t. It only knows what’s been done before. It’s autocomplete with a superiority complex."

@mbroome @llorenzin It definitely appeals to my ego. But I find myself swapping in "ReactNative" for AI, and it rings exactly the same. Or VueJS. Or Visual Basic. Or COBOL. Every time we've lowered the bar to entry and let folks get way out beyond what they actually understand.

They've built crap.

And they've built incredibly useful things that no one would have built if the barrier weren't so low.

And they've built crap that also is incredibly useful.

(And also just crap.)

1/

@mbroome @llorenzin The funny thing is, working with these systems, the rant is surprisingly backwards.

I constantly have to fight with these AIs to *not* "worry about performance." They *love* to worry about performance. Add caches. Add lazy evaluation. Do weird things to save a few ms here and there. And in the process make the code way too complex (and ironically probably slow…it's a common beginner mistake).

But they know more about cache lines than almost every dev. That I'm certain of.

@mbroome @llorenzin But folks should talk me about it another day when I'm not writing:

"You MUST NOT create a special rule just for measure 29 of this one file! This requires a general fix."

Seriously. Checking "are we in measure 29? Then assign the note slurs correctly for that one measure because we can't figure out how to do it right."

I…

*THIS* is our AI overlord?!??!!?

(But also, it's pretty incredible when IT'S NOT TOALLY CHEATING ABOUT EVERYTHING!)