Letting your text editor write your code, not using version control… I don’t feel sad at all. Hope lesson was learned.
Git wasn’t the first version control software. I remember using sccs back in 1991 and apparently it was written all the way back in 1972 https://en.wikipedia.org/wiki/Source_Code_Control_System
I made a game engine and a game back in highschool, but all that code is lost because I didn’t know how to use git. I knew git existed (and even knew enough to know it was better than mercurial or svn), but I was too lazy to learn.
Don’t trust anyone who can’t spell ‘oops’.
Maybe he was cursing the god of dev ops
Nah his opps fucked up his backup.
His operations department?
Fake developer doesn’t use version control. Big surprise.
I just want to pause a moment to wish a “fuck you” to the guy who named an AI model “Cursor” as if that’s a useful name. It’s like they’re expecting accidental google searches to be a major source of recruitment.
It’s not an AI model, it’s an IDE
My comment stands
“Developer”
“my” 4 months of “work”Those are the ones easily replaced by AI. 99% of stuff “they” did was done by AI anyway!
Acts like SVN and CVS didn’t exist
Also like Reddit did
Don’t worry, I’m sure Cursor will be able to clobber your git history and force push to master any day now
Genuine question: what would it take to poison an LLM with ai tools to run
git push --force origin mainorsudo rm -rf /we just need a little more AI
You know, none of the “AI is dangerous” movies thought of the fact that AI would be violently shoved into all products by humans. Usually it’s like a secret military or corporate thing that gets access to the internet and goes rogue.
In reality, it’s fancy text prediction that has been exclusively shoved into as much of the internet as possible.
At least they were humble and didn’t blame it entirely on Cursor… they also blamed Claude.
Forget git. Sending zip files into discord once in a while it the way to go.
Congrats discord now owns your code forever
I’d feel sorry for them. My personal projects will only harm them.
Not if you encrypt the zip.
And then make sure to send the encryption key over discord so that the recipient can read it.
Especially if they’re .zip files full of military secrets.
I’m not in any war thunder servers.
this guy would have force pushed onto main about 10 mins after this if he did have git
And then lost the reflog by
rm -rfing the project and cloning it again.God bless DCVS.
Tbf you have to do that for the first push, if a Readme file was autogenerated
You don’t if you just clone the repo you created.
Huh? I’m talking about existing code being in a dir, then initting a git repo there, creating a pendant on your hoster of choice and then pushing it there. Wouldn’t cloning the repo from step 3 to the code from step 1 overwrite the contents there?
There are multiple solutions to this without using --force.
Move the files, clone, unmove the files, commit, push being the most straightforward that I can summon at this time… but I’ve solved this dozens of times and have never use --force.
If your remote is completely empty and has no commits, you can just push normally. If it has an auto-generated “initial commit” (pretty sure Github does something like that), you could force push, or merge your local branch into the remote branch and push normally. I think cloning the repo and copying the contents of your local repo into it is the worst option: you’ll lose all local commits.
If it’s a single, generated, “initial” commit that I actually want to keep (say, for ex I used the forge to generate a license file) then I would often rebase on top of it. Quick and doesn’t get rid of anything.
You can also just tell GitHub to not do that.
True, in the situation with a local history maybe it’s worthwhile to --force to nuke an empty remote. In that case it is practical to do so. I just typically like to find non-force options.
Yeah, I was thinking of a new repo with no existing code.
In your case you’d want to uncheck the creation of a readme so the hosted repo is empty and can be pushed to without having to overwrite (force) anything.
deleted by creator
Does that still happen if you use the merge unrelated histories option? (Been a minute since I last had to use that option in git)
Never have heard of that, but in the case of you also having a Readme that will be even more complicated, I imagine. So just adding -f is the easier option.
Just save your prompts and vibes in a Google doc dude
Good thing it’s deterministic, oh wait 😃
You could literally just save a copy to your desktop before you’re going to do something sensitive.
That’s why I take a screenshot of my desktop before something stupid just in case.
Or use VCS like a normal dev
ok boomer
The first version control system I ever used was CVS and it was first released in 1986 so it was already old and well established when I first came to use it.
Anyone in these past forty years not using a version control system to keep track of their source code have only themselves to blame.
CVS was, for the longest time, the only player in the FLOSS world. It was bad, but so were commercial offerings, and it was better than RCS.
It’s been completely supplanted by SVN, specifically written to be CVS but not broken, which is about exactly as old as git. If you find yourself using git lfs, you might want to have a look at SVN.
Somewhat ironically RCS is still maintained, last patch a mere 19 months ago to this… CVS repo. Dammit I did say “completely supplanted” already didn’t I. Didn’t consider the sheer pig-headedness of the openbsd devs.
“We’ve always done things this way, we ain’t changing!” - some folks in the Foss community, like those RCS maintainers
We still use RCS at work. For config files for our network monitoring. Works fine still.
Pretty sure GTA V use(d) SVN or something like that. I remember reading the source code and being surprised that they didn’t use GIT.
Game developers often use Perforce instead of Git. Maybe it was that?
You definitely need something else than git for large assets, yes, its storage layer is just not built for that and they way art pipelines generally work you don’t get merge conflicts anyway because there’s no sane way to merge things so artists take care to not have multiple people work on the same thing at the same time, so a lock+server model is natural. Also, a way to nuke old revisions to keep the size of everything under control.
That’s very possible.
which is about exactly as old as git.
Wdym by that?
And Claude, off course.
Before that, it was RCS, released in '82.
Or gnu arch
Luckily I’m young enough that I never had to use RCS.
My first one was Visual Source Safe.
I will never go back to it for any amount of money.
You know, CVS wasn’t really that bad, just primitive and outdated.
I remember SVN
I want to forget SVN
I run a svn server at work
My condolences
I never understood the SVN hate. Then, as now, the problems are almost never caused by the tools, and almost always caused by the people misusing them.
I never got around to using anything except git, partly because of all the hate people would throw at the other competitors back in the day. Even if the criticisms were not fair, and even if it was all a secret conspiracy to kill git competitors, it definitely worked out for the best. Imagine the hell we’d be in today if we had to constantly deal with different VCS solutions.
I want SVN little explorer icons back! I want to forget Jazz RTC.
That’s tortoise, and have I got news for you: tortoisegit exists.
