> if I could wrangle Claude into communicating exactly as I would have, the practical difference is of course not observable. But that's never happened, and I've had an enterprise license at work for years.
Sorry to say, but this is a skill issue (and not necessarily with using Ai). I've used Ai MANY times to help SIGNIFICANTLY improve things that I've written - from a few sentences to many paragraphs.
As I've said in other comments, it'll rapidly and effectively remove all my worst tendencies. And, likewise, sometimes I'll have it write a first draft when I give it appropriate context/guidance that I can't be bothered to fully curate/synthesize. Then, once it gets that draft, I'll take over and tidy it up. You might say that the "can't be bothered" part is the entire issue, and I'll again say that what matters is the final result - a master chef or chief architect is not doing all the grunt work...
> Sorry to say, but this is a skill issue (and not necessarily with using Ai). I've used Ai MANY times to help SIGNIFICANTLY improve things that I've written - from a few sentences to many paragraphs. As I've said in other comments, it'll rapidly and effectively remove all my worst tendencies. And, likewise, sometimes I'll have it write a first draft when I give it appropriate context/guidance that I can't be bothered to fully curate/synthesize. Then, once it gets that draft, I'll take over and tidy it up.
Isn't this contradictory? Why do you need to take over if it's doing such a good job?
>Sorry to say, but this is a skill issue
That's the same slop response as "it's a skill issue" applied to C codebases being inherently insecure due to the language's footguns/design.
Your writing tendencies must be quite bad if Claude's tendencies are an improvement. Isn't writing a skill issue?