211–220 of 257 posts
Earlier quoted context omitted.
Deletes off your computer. I'm don't know what else they might be doing with it. They keep slimmed down summaries (on your comptuer) I believe but not the full context.
Then just copy the files into another directory, or maybe include it in a VCS?
I don't see any issue with this at all. I noticed it the other day and thought it was convenient. The same way I let the agent tag the PRs/commits with its name. I want to know what was used, in fact I wish it would identify the model used. I'm not embarrassed by my LLM usage and I want to provide a full audit trail whenever possible to aid myself in the future. PS: Claude archives old conversations on your computer…
> PS: Claude archives old conversations on your computer after 30days Does adding this to your Claude settings.json not work anymore? { "cleanupPeriodDays": 99999 }
Earlier quoted context omitted.
I disagree with this. The code alone is not the artifact. How you came to the decision to write the code in a certain way is certainly an important artifact of the development process. Otherwise how would your coworkers know whether or not a particular piece of logic is still relevant?
How did you before LLMs 3 years ago?
Fwiw i don't like a session link in the commit message, because of link rot reasons.
I may be missing something, but this is exactly what I want as a default. I want the session links there. I see PRs from my coworkers with session links. I still get to control whether other people can see the session, but I don’t lose it. I don’t get the “unprofessional” argument. This is attribution. Attribution is professional. If you don’t want it, you turn it off or rewrite the commit messages. If you are having…
Do you put IDE attribution in your commits? Attribution is silly, AIs are hammers not interns.
Though reading you yelling at the bot and calling it a Clanker might elicit a chuckle from me.
Earlier quoted context omitted.
Do you imagine China may one day claim they own all the rights to all the objects labeled with “Made in China” on them? Could Anthropic possibly do this?
I would say the answer is "obviously not," to the degree that it's hard totake your question in good faith. The China-made goods have been sold. Ownership transfers at sale. It would be ludicrous for some Chinese agency to say, "Well, we made it, so even though you bought it from us, it's actually still ours. Surprise!"
Earlier quoted context omitted.
Nah, "provenance" is a good word to know. Plain English version would be, "what colour are your bits?".
Good word to know, yes. Best word to use, no. If you know “origin” or “source” and those words suffice, using a word that means the same thing but you don’t know is strictly worse for communication. So if Claude is writing a novel, maybe provenance is the best word to use at times. If its a codebase README or variable name, its usually not.
Earlier quoted context omitted.
My spade is a meaningful part of digging a hole when I plant a tree, but I still don't want a "Spear and Jackson" sign on my tree when I'm done.
There has been more than I project where I literally didn’t even look at the code. I prompted what amounts to verbose “I want X” and then did QA. I’m perfectly happy with an LLM being credited with that code and there being no copyright existing for that code. For some people that is their life’s work and they want to clutch pearls. Their sole contribution was a half baked idea and they shipped QA out to their “users…
Something you’ve created from nothing because of the tool you’ve used to create it should not be allowed to be licensed?
The major problem I see with these are linkrot. Do any of us truly believe these links will work 30 years from now? Post IPO, many years down the line, a leadership that is eager to cut costs will look at their storage usage and expire 7 year old non-training sessions. Quickest thing to go. I have zero faith in any successful provider getting this right. Git is supposed to be the durable storage medium, self containi…
I can't imagine a project so wildly successful and stable that the session URL in a commit history is relevant after 5 years, let alone 30. Git is only 21 years old. I'm not deciding team policies with a multi-decade view. That said, I wouldn't agree with using the session URL as the entire commit message, or even with letting the session URL make up for other missing details. But to me it's an at-worst neutral chang…
I can't believe how many people are in favor of it. Like it's so positive in the comments I'd think it's astroturfing. The code is the result of my work however it got done, and if I don't document or explain it well enough then that's a separate issue. Did you want to see my slack messages to my mentor too? Or how about all the stack overflows I read? Maybe I should voice record all the times I swore about Gary the…
Are they relevant questions? I've often commented on lines of code in a PR that "so and so gave me the idea".
> Or how about all the stack overflows I read?
Would be nice to link to them either in a code comment (if they're not changed very much) or again somewhere in the PR discussion
> Maybe I should voice record all the times I swore about Gary the junior dev not documenting something?
If you noticed something severely lacking that would help other people out if that wasn't the case then yes I hope you would bring it up?