It gets the axe because, like a lot of support roles, if it works then it’s “what do we pay you for” and if there’s a bug then it’s “what do we pay you for”. Any time that there’s a leadership member doing bean counting instead of actual product quality it’s one of the biggest targets for the funding axe.
“We just won’t program in bugs”, oh okay sure buddy.
“AI can catch all the bugs”, uh huh.
“Customers won’t see most of the bugs, it’s not worth the time and money”, yep.
“What do you mean players don’t invest time in something that can break for no reason”, that’s what we told you months ago.
“QA should have caught this, how did we miss this??”, there’s two QA and they’ve been pulling 80 hour weeks for a year, they did. it got put in the backlog to hit arbitrary deadlines.
“This bug is unacceptable, what does QA even do?” gestures at pile of hundreds of other system breaking bugs that they caught before this one edge case that got missed in the dumpster fire of development
It gets the axe because, like a lot of support roles, if it works then it’s “what do we pay you for” and if there’s a bug then it’s “what do we pay you for”. Any time that there’s a leadership member doing bean counting instead of actual product quality it’s one of the biggest targets for the funding axe.
“We just won’t program in bugs”, oh okay sure buddy.
“AI can catch all the bugs”, uh huh.
“Customers won’t see most of the bugs, it’s not worth the time and money”, yep.
“What do you mean players don’t invest time in something that can break for no reason”, that’s what we told you months ago.
“QA should have caught this, how did we miss this??”, there’s two QA and they’ve been pulling 80 hour weeks for a year, they did. it got put in the backlog to hit arbitrary deadlines.
“This bug is unacceptable, what does QA even do?” gestures at pile of hundreds of other system breaking bugs that they caught before this one edge case that got missed in the dumpster fire of development