4 ms·

yes, curious why he was fired for? Maybe he reported it too late ...

sidman 15y ago
This happens all the time. Some people at the top just want to hear good news even though its false news. If there is one individual saying dont ship and they ship it, if it roots up after its been released the 2 get fired cause 1 - the marketing guy didnt listen to advice 2 - the developer introduced the problem If the person giving the advice isnt there to say "Hey i already told them that ! but they didnt listen" they can declare it as a mistake or an unknown bug. Usually people dont get fired for an unknown bug and dont look "as bad" as if they where told and chose to ignore it. Happened at my work a few times, engineer didn't get to the point of being sacked but when the severity 1 solution was ignored in preference of another more "stupid" solution proposed by business types the engineer that suggested the proper solution was never invited to meetings anymore. Then when the initial solution didnt work and used the said engineers solution they didnt even tell him they implemented it until weeks later when he found out indirectly. [edit] hmm, after reading it again, its either what i wrote above or someone lied and said QA didnt find any problems so we shipped it based on their recommendation(which in my opinion is worse then a way to keep his mouth shut)
dholowiski 15y ago
Sounds like they shotthe messenger
- candre717 15y ago
  Embarrassing business practices.
  - rokhayakebe 15y ago
    Which happens a lot more than you think.
- slipperyp 15y ago
  Who is the author protecting by not sharing any actual details? I anticipate an update to the post: "The game shipped. I got fired from my job at Dairy Queen in high school, but that's another story!"
tomfakes 15y ago
Based on the context of the article, he was a QA person in a triple A game company. It seems to be standard practice to let most of the QA teams go once the game has shipped, as most of these guys are contract, not full time.

This happens all the time. Some people at the top just want to hear good news even though its false news. If there is one individual saying dont ship and they ship it, if it roots up after its been released the 2 get fired cause 1 - the marketing guy didnt listen to advice 2 - the developer introduced the problem If the person giving the advice isnt there to say "Hey i already told them that ! but they didnt listen" they can declare it as a mistake or an unknown bug. Usually people dont get fired for an unknown bug and dont look "as bad" as if they where told and chose to ignore it. Happened at my work a few times, engineer didn't get to the point of being sacked but when the severity 1 solution was ignored in preference of another more "stupid" solution proposed by business types the engineer that suggested the proper solution was never invited to meetings anymore. Then when the initial solution didnt work and used the said engineers solution they didnt even tell him they implemented it until weeks later when he found out indirectly. [edit] hmm, after reading it again, its either what i wrote above or someone lied and said QA didnt find any problems so we shipped it based on their recommendation(which in my opinion is worse then a way to keep his mouth shut)

dholowiski 15y ago

Sounds like they shotthe messenger

candre717 15y ago
Embarrassing business practices.
- rokhayakebe 15y ago
  Which happens a lot more than you think.
slipperyp 15y ago
Who is the author protecting by not sharing any actual details? I anticipate an update to the post: "The game shipped. I got fired from my job at Dairy Queen in high school, but that's another story!"

tomfakes 15y ago

Based on the context of the article, he was a QA person in a triple A game company. It seems to be standard practice to let most of the QA teams go once the game has shipped, as most of these guys are contract, not full time.