Anthropic's public writing style is very different from Claude's because it's written by humans. Even in their job ads they ask candidates to not use AI for any writing (or at least they used to).
I find the language of "collaborating with Claude" off-putting. I don't collaborate with Claude, I use Claude. It's a tool in my hands, not a colleague or a friend.
AI companies seem eager to perpetuate the fantasy that all users carefully review all LLM output, and supervise all tool calls.
Anthropic certainly isn't planning to take responsibility for Claude's mistakes - that's the user's responsibility. Describing everything as 'collaborating' is I think part of their efforts to emphasise the user's role in the process.
I think the opposite. AI Companies use the term collaborate to increase the trust in the LLM output.
I trust the output of colleagues I am collaborating with and have an assumption of some shared responsibility. But if I use a tool like numpy/matplotlib then I am accountable for the conclusions I come up with. I can't make an excuse that "matplotlib" created a plot so my decisions were incorrect and not due to my own negligence.
I’ve read the link, but I don’t get how it’s relevant to the OP’s point that Anthropic public communications don’t sound like Claude. Can you enlighten me?
Ive given up trying to fight claudes language, and Im afraid Im getting used to it and can even understand what claude is saying faster or should I say I can parse it faster now.
whats troubling here is that one of the anthropic devs on twitter or github don't seem to acknowledge this issue, If they don't acknowledge there's nothing for them to fix
Anthropic certainly isn't planning to take responsibility for Claude's mistakes - that's the user's responsibility. Describing everything as 'collaborating' is I think part of their efforts to emphasise the user's role in the process.
I trust the output of colleagues I am collaborating with and have an assumption of some shared responsibility. But if I use a tool like numpy/matplotlib then I am accountable for the conclusions I come up with. I can't make an excuse that "matplotlib" created a plot so my decisions were incorrect and not due to my own negligence.
Do I need a different reason?
name= a variable name or fields
load bearing= coupled dependencies that can break other things if you change it
Every damn Claude article does the “tell ‘em what you’re going to tell ‘em, tell ‘em, tell ‘em what you told ‘em” routine.
Not sure I agree about e.g. GPT not sounding this formulaic though, imo it definitely does.
I don't actually have a problem with the common terms Claude emits, I think they're appropriate for a coding agent. But I do find them overused.
/s?