{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
6/21/2016 12:04:43 AM
192
If you do not know how to program games...
Keep your mouths shut about everyone at Bungie screwing up.
There is so much to programming it's not funny. Fixing one mistake can lead to making 5 new ones.
It's never ending to keep a game perfect the first time otherwise no game would ever be released.
Please keep your patience and wait it out. If you're still playing Destiny to this day, you can wait out another week for Iron Banner. Unless you want to program it for them, then let them do their job.
Bitching does not speed up the progress and I guarantee many of you would rather actually play it rather than consistently get kicked.
English
#Destiny
-
작성자: Swiftlock 6/22/2016 7:50:33 PMDoesn't matter whether or not you can program. Bungie did screw up, and the players have the right to call them out because they want to see the game get better with all the untapped potential that it has. Deal with it.
-
6 답변99 little bugs in the codes 99 little bugs Take one out, patch it around 117 bugs in the code
-
5 답변Ok, programming is a tough gig. If only there were some kind of testing that could be done before putting a patch or add-on in effect...
-
Every profession has something that someone else can't do. It's just in most places if you keep stuffing up in your position you get asked to leave. The thing is they are not only causing problems for them they are causing problems for the whole team.
-
2 답변[quote]Keep your mouths shut about everyone at Bungie screwing up.[/quote] hey dumbass .. I PAID THEM NOT TO -blam!- UP!!!!!!!!
-
2 답변작성자: Devasstator 6/22/2016 2:03:55 AMYeah fixing one mistake can lead to ripple effect impacts through code, but that simply means you built a bad engine, API, DBs, etc or you have poor integration between units. This engine seems plagued with the common issues that Waterfall or BRUF planning and development have been identified with for over a decade. Adopting a more XP/Agile delivery model would actually help solve a lot of the issues they discussed in their GDC presentation. Like it or not, there are a bunch of screw-up happening due to a poorly programmed engine. They probably didn't use test-first programming, pair programming or a 10-minute build. All of these things (or many others) would help prevent this kind of sloppy quality control before they impact their users experience. I don't see the point in getting overly angry about IB being cancelled as it's ultimately just a product with a broken feature right now and there are LOTS of other great games to play out, BUT the customer does have a right to voice their discontent at the manufacturer of the product. It WAS A SCREW-UP. Screw-ups happen, that's part of business. Also, staying mute about things that bother you about your service/product achieves less than voice concern about it.
-
2 답변IF YOU CANT WORK A GRILL Keep your mouths shut about me not cooking fast enough. There is so much to cooking it's not funny. Fixing one mistake can lead to making 5 new ones. It's never ending to keep a burger perfect the first time otherwise no burger would ever be released. Please keep your patience and wait it out. If you're still cooking burgers to this day, you can wait out another hour for them to cook. Unless you want to cook it for them, then let them do their job. Bitching does not speed up the progress and I guarantee many of you would rather actually eat your burger rather than consistently get burned ones.
-
IF YOU DON"T KNOW HOW TO DESIGN AND BUILD CARS... Keep your mouth shut if you or a loved one are injured or killed due to an issue that leads to a safety recall. Because that's the moronic standard we will live by. We can't expect professionals specialized in a particular field to be any more competent than a layperson.
-
Having what should be first month, maybe quarter, MAYBE YEAR... issues this late in a game is pretty crazy. The "fix one thing, five more problems pop up" analogy no longer applies. If the developers are still struggling with their own toolkit to the point where it is breaking matchmaking this much later... that's messed up. There is something wrong with the engine, the staff, or a combination of all. You don't accept rookiee mistakes this long into the pro season.
-
No offense, but most companies have to thoroughly test their code before implementation. In my line of business, a software bug can blow a hole in the earth. Bungie has the luxury of letting its players be the testers and acts accordingly.
-
Youre right, i dont know about "code". What i do know, is that most companies test a product before they release it. Even when they make a "fix". Its standard protocal to ensure that the system wont crash. There are how ever "bugs" that are sometimes overlooked and these are found more easily by the customers. "Bugs" are ussually found quickly and fixed. If the bug is embedded to deep then the previous update is reinstalled until the current can be repaired and reintroduced, thats barring that the previous code wasnt worse off. Im patient and can wait but there are many that dont understand and are just voicing thier frustrations. Try to ignore the hateful rants and dont fuel the fire. It'll all go away soon enough.
-
That's not the point, bud. Most logical people realize that there's a lot that goes into designing and programming a game. The issue is that these are people who went to college and make a living off of this. They have the experience to do this sort of stuff in a simple fashion, and they just don't. They're messing things up that are common sense, and that's not something that should be supported.
-
5 답변I work in software development. The thing is, it does not matter how complicated it is. Deadlines are deadlines and the finished product should be polished and largely bug free come the end of that deadline. All I'm saying is that in my career, the excuse: [quote]programming is complicated [/quote] Is never acceptable in any situation.
-
Dude shut up. Of course programming is complicated, but they are professionals, and it is their job to understand how to put out a polished product, and not release updates before they're fully completed. They didn't test their update well enough before they released it, and now everybody has to pay for it.
-
24 답변I'm no auto engineer but if i bought a car and it didn't work, i don't have the right to complain about it? It's a business and their product has problems. So i have a right to complain about what I've paid for.
