What’s this supposed to mean? I’ve done similar things when restructuring my code. Git tries it’s best to keep track of files changing directories but sometimes you just go fuck it and abandon the history because Git is being a git.
I’d be more concerned about consistent 10k+ changes per day or something
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?
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.
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.
What’s this supposed to mean? I’ve done similar things when restructuring my code. Git tries it’s best to keep track of files changing directories but sometimes you just go fuck it and abandon the history because Git is being a git.
I’d be more concerned about consistent 10k+ changes per day or something
10 million LOC addition in one month is not a red flag to you?
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?
Meh. I’ve seen (and done) worse, honestly. Again would be more concerning if they kept it up
… 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.
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.