> I'm not asking for anecdotes. I'm asking for actual real proof.
I gave you real proof: real research in this field on the exact subject matter WITH data.
> You're really going to use papers from 2023 and 2024?
Vs what? Nothing? Ok, prove them wrong. anecdotes aren't proof
> I'm not even understanding your line of questioning here.
I've disproven your claim 3 times. You're not understanding anything because it goes against your narrative. If you didn’t write the code and you didn’t write any documentation about the code, then you have no proof that you know anything about said code base.
> Dude, maybe it's YOU guys working on small codebases
You're projecting. You can't vibe code large projects. It's not sustainable. if you are actually vibe coding actual large projects blind, it's only a matter of time before things go really wrong.
I gave you real proof: real research in this field on the exact subject matter WITH data.
> You're really going to use papers from 2023 and 2024?
Vs what? Nothing? Ok, prove them wrong. anecdotes aren't proof
> I'm not even understanding your line of questioning here.
I've disproven your claim 3 times. You're not understanding anything because it goes against your narrative. If you didn’t write the code and you didn’t write any documentation about the code, then you have no proof that you know anything about said code base.
> Dude, maybe it's YOU guys working on small codebases
You're projecting. You can't vibe code large projects. It's not sustainable. if you are actually vibe coding actual large projects blind, it's only a matter of time before things go really wrong.