Let’s do coding shall we? How about I just tell my editor, verbally or in writing, “refactor this method so that it does this and that and then update all call sites project-wide”? Or “would invariants of this program break if I do such and such”.
Or my DAW: “add a bit of dark plate reverb to the guitar, and fade out in the end”, or “isolate guitar and slow down the track in this file, and then loop this lick, I would like to learn it; oh and also tell me where I’m not playing it correctly”. Or “give me a backing blues track without the guitar that’d fit this chord progression”.
All of that without necessarily training the model exhaustively to do every combination of these things.
We could make programs _so much_ better than they currently are, it’s not even funny.
IMHO, that's what the author is arguing. Now that we have the tech to do it, this is how companies will win new users. Making the technology "better" means subjective design decisions that can be defined as tasteful when done well.