590
Discord’s Second Attempt To Roll Out Age Verification Is Going Badly (kotaku.com)
submitted 1 week ago by to c/technology@lemmy.world
121 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] 1 point 1 week ago (5 children)

10 million LOC addition in one month is not a red flag to you?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 5 child comments
    •
  • [–] 21 points 6 days ago*

    Not when it's a fucking private to public merge. Why the fuck would a tiny public repo that was basically a elevator pitch in code base form send up red flags when you merge in the actual product that includes the better part of half a year worth of development from a team of people?

    Are you allergic to context and critical thinking? Or do you enjoy just being paranoid?

  • permalink
  • fedilink
  • source
  • parent
  • [–] 7 points 1 week ago (3 children)

    Meh. I've seen (and done) worse, honestly. Again would be more concerning if they kept it up

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] -3 points 6 days ago* (2 children)

    .... What?

    I'm incredibly productive, and have had the joy of working on productive teams. And unless they are working with hundreds of full time, high performing, engineers. You ain't changing 10 million lines in a month.

    With AI, it's technically possible, but I can only imagine the slop. It's likely incomprehensible at this point.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 7 points 6 days ago* (last edited 6 days ago) (1 child)

    Just speaking from personal experience. Here's a story.

    One time I did a massive refactor, basically touching every function in the software. For background, this was a massive enterprise application. The backend was about 10 million lines of code, the front end was… probably triple that, I didn't bother counting. Yes, building the code took more than an hour, even on extremely beefy machines.

    The reason for this refactor was there was a huge amount of tech debt that finally caught up to us. You know, putting it off for years, using deprecated functions and old methods, feature flags, even forking software and modifying it to be compatible. Just years of finding creative solutions, until finally things said "enough" and there was no more bandaids. I was given the green light to fix up everything at once. Programmer's wet dream, at least for me; I was so happy.

    Anyway, in this project, we did rebase not merge. So, after 3 months of working diligently in a branch; I had to rebase the whole fucking thing because my coworkers obviously weren't idle that whole time. This part I didn't enjoy so much.

    It took 2 weeks to rebase all the merge conflicts. It took so long, I had to rebase again. Multiple times. Each rebase getting closer and closer to being able to finally merge into master.

    Finally I did it. I told everyone else to just relax and take the day off, while I merge into master and fix all the problems. There was many problems of course. But the final commit was tens of millions of lines of code changed, all by myself. This was before LLMs. But I have the type of brain that can sit there for 9 hours straight every day and tidy up code and enjoy it.

    Edit: just to clarify, "rebase" makes it look like all those changes happened at once instead of spread out over months, and would make a huge spike like that. Also just because LLM wasn't a thing didn't mean I did it all manually… I heavily used find-and-replace, upgrade scripts, codemod, and many other automation tools. I think I even wrote a few manual codemod scripts to get it done.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •