Vibe coding absolutely does not work at the scale of an EA Sports game. Even if it could get to a compileable state, there will be loads of performance and memory issues. The kind of code needed for these codebases aren't exactly going to be scraped on Github.
And then there's console code rooted in NDA's. Throwing that into an LLM is a great way to be blacklisted as a publisher.
I buy that vibe coding doesn't work at that scale, and there will always be an investor that thinks it does (these aren't being led by traditional tech investors) who's willing to pay, thinking there's an opportunity.
The NDAs don't matter. If there's an exception for tooling like Github, that'll be enough, and enterprise AI code platforms will all hear the same concern and say they don't retain anything. What does matter is there isn't much training data on programming for modern consoles.
Tools like Git are fine. A 3rd party server like Github is an entirely different playing field. For console SDKs I wouldn't even trust a private Github account. There's a reason the industry standard is whipping up your own perforce server instead.I'm doubtful they'll make an exception for a company that wants to train on their data without consulting them.
But this is all speculation. I haven't seen a recent SDK that talked about these issues, so maybe this is already talked out
And then there's console code rooted in NDA's. Throwing that into an LLM is a great way to be blacklisted as a publisher.