I do tend to agree. Though at the current pace of change I don't know if we can take it for granted.
As a recent example, I was on a chat with the two most experienced technical people in our company and the original developer of a feature trying to work out why we were getting a null pointer exception in a very specific case. Of course we had a fix, just a guard against the null pointer, but I'm always uncomfortable with not knowing the underlying cause.
I kept digging while someone promoted the fix. Eventually ruling out two of our original theories as to why it happened. Until eventually someone just asked Cursor which spit out a theory which matched the symptoms perfectly and which we quickly reproduced locally.
I still think we'll need some kind of human who lives in that wide space between the 95% of the population who couldn't get Excel to sum a list of numbers and the machines but the industry will be unrecognisable.
In my experience the LLM when given the ticket would have done the original null pointer guard fix given the bug. Only under direction does it ever dig deeper and for me it'll often go down some wrong paths unless I tell it to go somewhere else. It's great when it gets it right the first time. But that is rarely the case and usually you just get good enough if you don't care to go further.