DE version is available. Content is displayed in original English for accuracy.
Advertisement
Advertisement
⚡ Community Insights
Discussion Sentiment
50% Positive
Analyzed from 520 words in the discussion.
Trending Topics
#claude#anthropic#don#tell#writing#find#tool#actually#style#job

Discussion (16 Comments)Read Original on HackerNews
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.
Things like:
> Not allowed: Prompt: "Write my answers to the application questions for an AI safety researcher position at Anthropic." Result: Generic content with experiences you haven't actually had
I haven't seen other policy documents from them that as as relevant to the question anywhere else.
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?