362
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 13 Jul 2026
362 points (100.0% liked)
Fuck AI
7634 readers
641 users here now
"We did it, Patrick! We made a technological breakthrough!"
A place for all those who loathe AI to discuss things, post articles, and ridicule the AI hype. Proud supporter of working people. And proud booer of SXSW 2024.
AI, in this case, refers to LLMs, GPT technology, and anything listed as "AI" meant to increase market valuations.
founded 2 years ago
MODERATORS
Fork the repos that matter now, and squirrel them away somewhere, just in case someone gets froggy and gives Claude write access to your repos and fucks the history of something interesting like that. Always good to have a backup contingency.
I'm of the opinion that companies that make stupid AI decisions so they can fire people shouldn't get bailed out by a good decision made by one of the people they're planning to fire.
Let them burn.
Corporate suicide by AI?
My point is more along the lines of “some prudent sandbagging might let you swoop in and save the day at some future point when everything goes tits up”
My point is more along the lines of "Let things go tips up instead of incentivizing bad behavior by bailing them out of their fuckups."
A clone of a git repository is a full backup.
And then you accidentally pull / force pull or something and your “backup” is fucked.
Adding an extra step for a harder-to-find backup makes it more difficult to accidentally hose your known-good state.
I've seen cases where the commit was still there, even though there were no pointers (branches/tags) pointing at it. Which raises the question, when does git delete a commit?
By default, when it’s older than two weeks and you run any of the standard commands which trigger a GC check.
Docs here: https://git-scm.com/docs/git-gc
Commits are pointed to by references such as branch names. If a branch is deleted or a force push happens, the commit remains accesible for some time. It can be found in the "reflog". This works much like pointers and automated memory management. If no tag points at it, it will become garbage-collected at some point. Adding a tag like "non-ai-master" would prevent garbage collection.
this is one of the most common cases in which you want to mutate your history, and correctly excising content from a commit will change the commit shasum, and make the previous commit shasum (intentionally) irretrievable (from remote, at least). If the shasum doesn’t change, you haven’t removed anything.