At least they were humble and didn't blame it entirely on Cursor... they also blamed Claude.
this post was submitted on 21 Mar 2025
461 points (100.0% liked)
Programmer Humor
429 readers
10 users here now
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
Rules
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
founded 2 years ago
MODERATORS
this guy would have force pushed onto main about 10 mins after this if he did have git
Tbf you have to do that for the first push, if a Readme file was autogenerated
"Developer"
"my" 4 months of "work"
Those are the ones easily replaced by AI. 99% of stuff "they" did was done by AI anyway!
Before Git, we used SVN (Subversion), and CVS before that. Microsoft shops used TFS or whatever it's called now (or was called in the past)
Wasn’t it Visual SourceSafe or something like that?
God, what a revolution it was when subversion came along and we didn’t have to take turns checking out a file to have exclusive write access.
Visual SourceSafe
Yes! That's the one I was struggling to remember the name of. My previous employer started on Visual SourceSafe in the 90s and migrated to Team Foundation Server (TFS) in the 2000s. There were still remnants of SourceSafe when I worked there (2010 to 2013).
I remember TFS had locks for binary files. There was one time we had to figure out how to remove locks held by an ex-employee - they were doing a big branch merge when they left the company, and left all the files locked. It didn't automatically drop the locks when their account was deleted.
They had a bunch of VB6 COM components last modified in 1999 that I'm 80% sure are still in prod today. It was still working and Microsoft were still supporting VB6 and Classic ASP, so there wasn't a big rush to rewrite it.
load more comments
(1 replies)
Yeah VSS was the predecessor to TFS, and now TFS is called Azure DevOps... whatever the fuck that means, Microsoft needs to get it together with product naming. Anyway TFS sucks major rotten ass. I have my problems with git - namely user friendliness - but TortoiseGit has put all those troubles to rest.
Nothing like that can fix TFS.
load more comments
(2 replies)
I thought mercurial was older than git, but apparently it's 12 days younger.
And throughout it all was the tried and true v3.0-final-UPDATED-4
The best is when the version also had the name of an ex employee on it.
load more comments
(2 replies)
A place I worked at did it by duplicating and modifying a function, then commenting out the existing one. The dev would leave their name and date each time, because they never deleted the old commented out functions of course, history is important.
They'd also copy the source tree around on burnt CDs, so good luck finding out who had the latest copy at any one point (Hint: It was always the lead dev, because they wouldn't share their code, so "merging to main" involved giving them a copy of your source tree on a burnt disk)
TFS actually moved its core version control to Git in 2013 and was later was rebranded as Azure DevOps a few years ago
load more comments
(1 replies)
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.
load more comments
(7 replies)
And Claude, off course.
Ah yes, the elusive AI "programmers".
The vibes were off.
Yeah this what you get when you code based on vibes.
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.
load more comments
(2 replies)
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.
It's a scary amount of projects these days managed by a bunch of ZIP files:
- Program-2.4.zip
- Program-2.4-FIXED.zip
- Program-2.4-FIXED2.zip
- Program-2.4-FIXED-final.zip
- Program-2.4-FIXED-final-REAL.zip
- Program-2.4-FIXED-FINAL-no-seriously.zip
- Program-2.4-FINAL-use-this.zip
- Program-2.4-FINAL-use-this-2.zip
- Program-2.4-working-maybe.zip
- Program-2.4-FINAL-BUGFIX-LAST-ONE.zip
- Program-2.4-FINAL-BUGFIX-LAST-ONE-v2.zip
load more comments
(4 replies)
You need a USB C “Power Ctrl+Z” key. Unlike the regular Ctrl+Z key one of these bad boys is capable of reversing edits across system reboots until as far back as when you originally plugged it in.
load more comments
(1 replies)
subversion. those were the days...
Was my first experience with source control, a bunch of Gary's Mod mods were distributed that way, think I recall wiretool doing that, spacebuild was for sure, predated my work use by like 5ish years.
I didn't hate it but definitely prefer git, but I'll take literally anything over not having it,
load more comments
(1 replies)
load more comments
(1 replies)
Just a heads up, it you don't know how to use cli git in 2025 you're probably a shit developer. There are undoubtedly exceptions, but I would argue not knowing version control intimately makes you a bad developer.
Why learn an archaic and honestly horrifying command line interface, possibly the worst CLI ever made in the history of computing...when nice normal graphical interfaces work better, have discoverability, have troubleshooting tools, and don't require memorizing scripture?
Mate... Theres maybe like 5 "git + singleword" commands that cover 99.999% of all of your uses of git. Its really not hard.
The fact that you don't already know why and are dependent on GUI tools that you don't fully understand is the reason that you're probably not a very good developer.
Git is incredibly powerful. Knowing why and how is infinitely valuable. Nothing about git cli is archaic or even particularly difficult to understand. Also the man page is very excellent.
load more comments
(2 replies)
Most cli stuff is a lot easier than programming. If you can't use cli then by definition you're a shit programmer.
Of course if you simply don't want to use cli that's a different matter.
Because they are universally incapable of coming anywhere close to the full power of git.
I can't tell you how many times I've had GUI-only people ask me to unfuck their repo (fortunately not at my current job, because everyone uses the CLI and actually knows what they're doing). It's an impedance to actually learning the tool.
Ultimately any GUI is a poor, leaky abstraction over git that restricts many of the things you can do for little actual benefit.
There's nothing 'archaic' about git's CLI. I think you might just be opposed to CLI's in general, which is fine for a regular computer user, but paints a grim picture of your competency if you're a developer.
load more comments
(2 replies)
load more comments
(2 replies)
Acts like SVN and CVS didn't exist
I remember SVN
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
Why did the porn star become a network admin after retiring?
She was already an expert in load balancing
git push origin master # moron
view more: next ›