top 50 comments

sorted by: hot top controversial new old
[–] [S] 211 points 2 years ago

At least they were humble and didn't blame it entirely on Cursor... they also blamed Claude.

  • source
  • [–] 154 points 2 years ago* (14 children)

    this guy would have force pushed onto main about 10 mins after this if he did have git

  • source
  • hideshow 14 child comments
  • load more comments (12 replies)
    [–] 142 points 2 years ago*

    "Developer"
    "my" 4 months of "work"

    Those are the ones easily replaced by AI. 99% of stuff "they" did was done by AI anyway!

  • source
  • [–] 130 points 2 years ago (29 children)

    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)

  • source
  • hideshow 29 child comments
  • [–] 57 points 2 years ago (13 children)

    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.

  • source
  • parent
  • hideshow 13 child comments
  • [–] 48 points 2 years ago (3 children)

    The worst was when someone left for vacation without releasing their file locks.

  • source
  • parent
  • hideshow 3 child comments
  • load more comments (2 replies)
  • [–] 25 points 2 years ago* (4 children)

    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.

  • source
  • parent
  • hideshow 4 child comments
  • load more comments (4 replies)
  • load more comments (3 replies)
  • load more comments (14 replies)
    [+] 104 points 2 years ago* (last edited 7 months ago) (16 children)
  • [–] 32 points 2 years ago (9 children)

    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.

  • source
  • parent
  • hideshow 9 child comments
  • load more comments (9 replies)
  • load more comments (5 replies)
    [–] 89 points 2 years ago (2 children)

    Ah yes, the elusive AI "programmers".

  • source
  • hideshow 2 child comments
  • [–] 86 points 2 years ago (4 children)

    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.

  • source
  • hideshow 4 child comments
  • load more comments (4 replies)
    [–] 76 points 2 years ago (6 children)

    Forget git. Sending zip files into discord once in a while it the way to go.

  • source
  • hideshow 6 child comments
  • load more comments (2 replies)
    [–] 74 points 2 years ago (5 children)

    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
  • source
  • hideshow 5 child comments
  • load more comments (5 replies)
    [–] 68 points 2 years ago* (2 children)

    if this is real, that's the kind of people who should be worried about being replaced by an ai

    it's also Claude

    lmao

  • source
  • hideshow 2 child comments
  • [–] 23 points 2 years ago (1 child)

    Was playing around with it. It's neat tech. It's interesting all the side projects I can spin up now. It absolutely cannot replace an engineer with a brain.

    I've caught so many little things I've had to fix, change. It's an amazing way to kick off a project, but I can't ever trust blindly what it's doing. It can get the first 80% of a small project off the ground, and then you're going to spend 7x as long on that last 20% prompt engineering it to get it right. At which point I'm usually like "I could have just done it by now".

    I see kids now blindly trusting what it's doing, and man are they going to fall face first in the corporate world. I honestly see a place for vibe coding in the corporate world. However I also see you still needing a brain to stitch it all together too.

  • source
  • parent
  • hideshow 1 child comment
  • load more comments (1 reply)
  • [–] 56 points 2 years ago

    Fake developer doesn't use version control. Big surprise.

  • source
  • [–] 53 points 2 years ago (2 children)

    It's actually reassuring to see that despite all warnings and doomsayers there will still be opportunities for programmers capable of solving problems using natural intelligence.

  • source
  • hideshow 2 child comments
  • [–] 50 points 2 years ago* (5 children)

    Just save your prompts and vibes in a Google doc dude

  • source
  • hideshow 5 child comments
  • load more comments (4 replies)
    [–] 45 points 2 years ago (4 children)

    Don't worry, I'm sure Cursor will be able to clobber your git history and force push to master any day now

  • source
  • hideshow 4 child comments
  • load more comments (4 replies)
    [–] 43 points 2 years ago (1 child)

    Acts like SVN and CVS didn't exist

  • source
  • hideshow 1 child comment
  • load more comments (1 reply)
    [–] 42 points 2 years ago (2 children)

    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.

  • source
  • hideshow 2 child comments
  • load more comments (1 reply)
    [–] 42 points 2 years ago (7 children)
  • [–] 45 points 2 years ago (6 children)
  • load more comments (2 replies)
  • [–] 42 points 2 years ago (1 child)

    ~/Dev/Project/file.ext~2025-03-20-Backup-6

  • source
  • hideshow 1 child comment
  • load more comments (1 reply)
    [–] 36 points 2 years ago* (1 child)

    Ahh yes, programming by vibe. The vibe is always dumbass. Just steal code that has already been explained to you like everyone else.

  • source
  • hideshow 1 child comment
  • load more comments (1 reply)
    [–] 32 points 2 years ago (3 children)

    subversion. those were the days...

  • source
  • hideshow 3 child comments
  • load more comments (3 replies)
    [–] 31 points 2 years ago (8 children)
  • [–] 26 points 2 years ago (3 children)

    Don't trust anyone who can't spell 'oops'.

  • source
  • hideshow 3 child comments
  • [–] 20 points 2 years ago* (last edited 2 years ago) (2 children)
    load more comments (2 replies)
    [–] 20 points 2 years ago* (last edited 4 months ago) (12 children)
    load more comments (12 replies)
    [–] 18 points 2 years ago

    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

  • source
  • load more comments
    view more: next ›