Hacker News new | ask | show | jobs
by flohofwoe 26 days ago
This JSON-parsing problem is the least of Rockstars problems I think.

But I bet it happened like this:

- when the game was still in active development, it was maybe anticipated that the shop might have a couple dozen items, no problem even when the JSON parsing is extremely slow

- game is released, a separate maintenance team takes over, online mode is running for several years

- over time more and more items are added to the shop, and now maybe there are a thousands of items in that JSON file

- ...and when there's some 'accidental exponential' code in the JSON loader/parser the loading time gets worse and worse, what once was a few milliseconds is now minutes, but there was never a sudden regression after an update, just every week a little bit slower

- depending on the churn on the maintenance team, the current people on the team probably don't even notice an increase in loading time until they leave again for greener pastures, e.g. for them "it has always been that slow"

- management probably first read about the problem in the news ;) (which of course is a problem on its own - but as long as the money keeps flowing and the curves in Tableau go up and up, why should they even care... players apparently also endured it without bringing out the pitchforks)

2 comments

Although this is possibly true, at any time the dev team could've gone: "loading is slow man, can we just profile it and see if there's anything obvious?". To someone with access to the source code and a debugger, that's probably less than 30 minutes of time to go from zero to hero.

I've done this kind of stuff many times, and something like a json array taking minutes to parse would likely be very very obvious when looking at a trace.

The dev team is usually under immense pressure to deliver. This probably slipped under the radar to let all the other features get through.

The maintenance team probably maintains other games as well.

Then you add in the knowledge loss through the churning of developers and over time the organization forgets how things should be.

Again, you're not wrong, but none of those things are insurmountable. If the team is really so stressed it cannot spend 30 minutes, over the many year of the existence of that bug, that seems like a development environment close to hell.

Knowledge loss is precisely my point: there is very little a-priori knowledge needed to solve this, the guy who found the bug proves that.

Yea development environments are close to hell in game development, won't argue that.
Thanks for your insight its appreciated. I know I come across mean but Im just reminding everyone of simple facts that atleast contributed to all these problems.

I have nothing to do with Rockstar and wish them well, Im just saying that if I were management during these situations I would have quit or made a public apology. Its just what I feel I would have done. Regardless of the salary. I mean if one is mgmt they should take responsibility.

But maybe in late stage capitalism that is both an abhorrent and illogical idea.