{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
Edited by GrayWulf25:
2/20/2017 6:26:27 PM
22
The path they are continuing down is wrong, I don't know who is advising them.
I'm a developer. If you update Production with a patch and find it has that many inadvertent changes, you roll back the patch, correct it, re-test and re-release it. You don't try to convince the users that some of the inadvertent changes might be OK, let's see...
If you tried that, and the users were all rightly aggrieved at your incompetence and bad decisions, you would then create a new patch to correct all the changes that weren't supposed to be there. Not do that unwillingly and argue the case for keeping half of them. I've never encountered anything like this in 25 years of IT development
It's like Josh still cannot accept there was a big mistake that needs to be corrected. He is clinging desperately to the belief some of the inadvertent changes might be a good thing. It's amateur hour in the development department.
English
-
I'm a software tester, and I 100% agree. For those saying that they didn't intentionally do this... I'll remind you that they said it themselves... They just wanted to see what would happen. If this was to happen where I work, people would be escorted out the door.
-
...how true...
-
Well said.
-
[quote]The path they are continuing down is wrong, I don't know who is advising them. I'm a developer. If you update Production with a patch and find it has that many inadvertent changes, you roll back the patch, correct it, re-test and re-release it. You don't try to convince the users that some of the inadvertent changes might be OK, let's see... If you tried that, and the users were all rightly aggrieved at your incompetence and bad decisions, you would then create a new patch to correct all the changes that weren't supposed to be there. Not do that unwillingly and argue the case for keeping half of them. I've never encountered anything like this in 25 years of IT development It's like Josh still cannot accept there was a big mistake that needs to be corrected. He is clinging desperately to the belief some of the inadvertent changes might be a good thing. It's amateur hour in the development department.[/quote] I'am developer as well [spoiler]in Lego, AMA[/spoiler]
-
Im sorry to say this but I agree.
-
Edited by TheShadow: 2/24/2017 9:40:24 PMThis company is lazy and don't play their own game. They have been in business for over 25 years. This patch was done deliberately and showed Bungie how far they can get away with the crap they have pulled this last 2 years. There is no excuse for this game to be in it's current messed up state and it is disrespectful for this company to keep treating their fanbase like this.
-
Edited by Kevin: 2/28/2017 12:53:19 AMThat is just idiotic. You are saying that bungie is intentionally angering their fanbase specifically for the sake of goofing off and proving they can do what they want. Destiny is not in a bad state at the moment. I have been playing across several different accounts since day one; its current state is a good one. I think there may definitely be something to be said about special ammo, but not the patch entirely. The issue with special weapons is that they are so good at the moment that almost anyone can use them effectively. Need each special weapon slightly in pvp and increase special ammo so that skilled special users can still be effective.
-
OK lol that's why they are losing players right now at such an alarming rate. Before the patch matches were usually 6v6 now after patch it takes a whole lot longer to find a game and when you do it's usually 4v3 or 6v4 and most players on one team or the other are quitting. They basically killed their own game.
-
No they didn't. First of all, you have no actual evidence that they are rapidly losing players right now. Secondly, even if they are losing players at the moment, the stellar weapon balancing patch is not the primary cause. People leave during content droughts. Bungie is going to be announcing Destiny 2 soon, so they are devoting most of their time to that. People aren't all leaving because the game is "shit", people are leaving because we've done everything in the game right now and in the meantime, there are new games to play.
-
Agree 100 percent. Unprofessional. I can only assume they are trying to kill Destiny to ensure people move over to Destiny 2. Well guess what Bungie, your strategy is fatally flawed. You will drive away loyal players like myself. I have loved Destiny through many ups and downs, but the recent situation and your attempted 'recovery' is farsical!! I would laugh if it were not so sad.
-
Edited by Vreegval: 2/24/2017 3:24:15 PMAbsolutely. You nailed it perfect. These devs either don't know or are completely turning a blind eye to the very basic software development and release rules - don't roll out a product/patch with bugs and if you do roll it back; and you got it spot on. Over the last 2.5 years the problem with Bungie is that they never address the actual issues and always try to fix the errors caused by actual problems. It's like trying to treat the symptoms and not the actual disease itself. I can say one thing for sure - if this dev team was in any other IT company, they would have been shown the door quite sometime ago.
-
"Amateur Hour" [i]Bungie[/i]
-
Right on
-
im not angry with them, but they just should have said they meant to do it cause THEY DID
-
Couldn't agree more. I'm a developer too and this would not be acceptable where I work. Rollback and fix the issue.
-
If you've viewed any of destiny's patches in the past (and all the bugs that come with them) you should already know that their development team seems inexperienced. That or they just don't test any of the patches, which is more than likely.
-
But that's the thing, they've worked with Halo long enough you'd think they'd know how to fix bug issues, or things simply not working. The whole concept of how matches are put together is still flawed, respawn positioning is really bad. Hit detection still a problem as well. They've had this program for, what, three years now, you'd think even in that amount of time they'd have more figured out. I just sit here scratching my head.
-
Therefore the question that needs to be asked is how many of the Halo devs are still around? When I have seen this type of thing before it was management meddling in the process, setting unrealistic targets, having little or no understanding of the issues, or just not caring beyond the bottom line. Treat your customers, who are your stakeholders, with respect and we will follow you; shows us a complete lack of respect and watch your reputation and investment shrivel and die. Sad, very sad ...
-
They are actively shitting all over us and they know a lot of people will continue to eat it all up like the chicks in 2 girls 1 cup.
-
I imagine that no one with sense is advising them. I'm not a dev but know that if a patch was made that caused unintended issues I wouldn't release that patch and hope for the best. Anyone with a brain can see that clearly makes no sense.
-
Ding! Winner.
-
Hey you finally decided to fix something! Only the whole damn game you have to fix now
