JavaScript is required to use Bungie.net

Forums

2/16/2017 10:44:03 PM
0
Two-thirds of my job is development management (admittedly not for gaming), and I get more exasperated by this screwup every day. Seriously, how could so many teams involved collaborate on this failure? Dev manager: poor risk assessment and/or assigned work to an unskilled resource. Developer: WTF no search for references to the property or method? Seriously?!? Unit Test: if that team exists, you guys are actually off the hook. The change to hungering blade did in fact update hungering blade. Not your fault. QA: sure, you can't test every event in the code, but you didn't think to test the other places the same functionality is provided? Was there even a regression test plan? Is it not updated or customized based on the code changes being delivered? UAT: Based upon how late this bug was identified, I'm actually going to give you guys credit for finding it. And assuming I'm right, you guys deserve a pat on the back. Community lead/ Management: Green lights a patch even though they know it contains 10 game-altering new bugs, all of which take away from the players' powers. Either there was a major failure by your community folks to convince management about the severity of the bugs and that they were showstoppers, or you did your job but management basically said "The customers can go screw themselves, we're not spending another dime on destiny 1." What the actual F!
English

Posting in language:

 

Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

You are not allowed to view this content.
;
preload icon
preload icon
preload icon