{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
10/30/2014 6:13:45 PM
1
I code for a living it's harder than people think. So many factors effect the coding. The biggest factor internal testing and going live to the public is when the bugs pop up.
During the internal testing everything is fine. Once it goes live to the general public then you find out the bugs it's crazy lol.
English
-
Edited by MortarGrunt06: 10/30/2014 6:24:17 PMYes, i understand that, I've been coding for as long as I've been gaming. Bungie should have known that too. The bugs started as soon as their first patch took effect, which was immediately. That should have tipped them off to the conflicts in their code, but no, they just said "let's see what happens." Then they patched again, and more errors came up. As they've patched, the problems have compounded. Any intelligent person would have STOPPED PATCHING and started reviewing the the patches to find the conflicting code that was causing the problems, not continued to write more code and add conflicts to an already conflicted system.
-
Lol that's true i can bet what you just said is happening right now at Bungie. That's the next phase in the coding process. I think that's why bad doo doo and thorn haven't received a buff yet. Most likely they are looking at the code for all guns. Since they coded the guns to effect PVE and PVP.
-
Yeah, so... Yeah. In the meantime, since I can't actually play the game through the patchwork code, I guess I'll go back to games that do work. That is my Destiny.
