The point of OP could be right but I decide to provide a counter example.
This morning I asked Claude to find why locale = empty string slipped into some of our customers records. Of course it's something I used to do myself but it did it in less than a minute. I couldn't match that speed, ever. Then I verified the analysis and the suggested fix. Finally I pasted Claude's analysis in a slack conversation, with attribution. I could have summarized what claude wrote to me, but it would be a waste of time because it was already pretty terse.
We decided to solve the problem in a different way but I think that starting with Claude's analysis was the right thing to do.
That's a best case scenario. My experience is that it's more common for an LLM to confidently predict incorrect solutions to the problem, and then you wind up wasting time chasing down wild geese. At those times, it winds up being more of a hindrance than a help.
This morning I asked Claude to find why locale = empty string slipped into some of our customers records. Of course it's something I used to do myself but it did it in less than a minute. I couldn't match that speed, ever. Then I verified the analysis and the suggested fix. Finally I pasted Claude's analysis in a slack conversation, with attribution. I could have summarized what claude wrote to me, but it would be a waste of time because it was already pretty terse.
We decided to solve the problem in a different way but I think that starting with Claude's analysis was the right thing to do.