Forum Discussion
If your car breaks down and the mechanic is already busy fixing another car, having all of the other employees at the dealership stop what they're doing isn't going to get your car fixed any faster, it's just going to make everyone else wait longer for everything else too.
This is a horrible analogy because not everyone at a car dealership is a certified mechanic, whereas the people working on new features and the people working on bug fixing are all software developers. Generally the only difference is in experience, in the context that the new team members are generally given bug-fix work as a way to get familiar with the overall codebase. Which is flawed logic, because it should be easier fix the bugs if people already familiar with the codebase. And if they would have started working on the bugs immediately instead of letting them fester for 10 years, this wouldn't be an issue.
Why is this such a problem? Any decent dev knows that you incorporate bug fixes into your next sprint, especially the more critical they are. It's a core tenet of Agile and DevOps. The only way it doesn't happen is when the product owner decides to let them fester instead of making sure they get addressed. I mean, even Bethesda fixes their bugs.
@undisputedloser wrote:If your car breaks down and the mechanic is already busy fixing another car, having all of the other employees at the dealership stop what they're doing isn't going to get your car fixed any faster, it's just going to make everyone else wait longer for everything else too.
This is a horrible analogy because not everyone at a car dealership is a certified mechanic, whereas the people working on new features and the people working on bug fixing are all software developers.
I highly suggest you take a look at the game's "credits" option in the save menu. There are artists and audio engineers and writers, not to mention many other people and teams who are most definitely NOT software devs. I also would tend to trust @EA_Cade's ability to describe the situation over someone not part of the Sims team, as he has direct knowledge of how the team is set up and run. Whether or not it's what the end user would like or agree with, there is no point in hashing it out over what it is. The teams do not get to decide who does what either, that's a corporate fact. I'm sure they are doing the best they can to make the game great under whatever limitations they are impeded by. And to be quite honest, it's a product I am happy to own and play with. I'm grateful for the attention it gets, even if I'm not thrilled when I encounter a bug either (and likely one that the team didn't encounter during allocated testing). The best we can do is keep working together to fix things that we notice. Yay community! lol