It doesn’t matter if it’s a designated job/role. The point is that the non critical activity of adding a nice to have feature (game) takes up resources that cannot be spend on need to have functionality such as FSD.
Except that's completely untrue.
The UI guy spending 10 minutes a few times a year adding games to the menu has
nothing whatsoever to do with the FSD guy writing or testing code.
They aren't the same person.
And neither is paid hourly.
One doing his job takes
no resources whatsoever that would go toward the other guy doing his, outside of the fact both of their computers run on company electricity.
As for the time aspect, keep in mind that the impact of adding a game is significantly more than one-time 10 minutes (or even a day)
No, it's not though. Your inability to understand how any of this works is rearing its head again.
, Not only does the game need to be developed / ported
Which is something
not done by anybody at Tesla so your continually bringing it up is nonsensical.
The atari games were developed decades ago, by people who are now elderly or dead.
The Linux atari emulation was developed in the late 1990s, by people who again are not Tesla.
Likewise the racing game was ported
not by tesla but its original developers. Same with Fallout Shelter which is being ported by Bethesda, not Tesla. Or Cuphead (I think I provided a link earlier where the original developer mentions THEY, not Tesla, are doing it).
, it requires testing implementation
Which the developer, not Tesla, would largely be doing since its them that would need to change their code if a problem is found.
I suppose the UI guy needs to test the game he added to the menu actually launches from the menu. That's about 30 seconds to test.
... maintained how exactly?
Are you under the impression Asteroids still gets monthly updates since originally written in 1979 or something?
The game and its integrations now also needs to be tested for compatibility before every system update
Not really, no.
Updating the neural net wouldn't have anything to do with how well Missile Command is functioning.
I suppose if you re-design the menus you'd need to test the launch buttons again though...another 30 seconds a game.
There might be rare MAJOR updates that'd require a few minutes of regression testing, once in a very blue moon...(like if they went to a new kernel or other major major OS change)- but you wouldn't have the dude who codes FSD doing
that either- you'd have interns and other cheap labor doing
widespread QA testing across everything in the car for such things.
. Ergo, the game consumes resources (in past, present and future) that will not be available for other activities (such as FSD).
Since the UI guy doesn't do FSD, this remains grossly incorrect.