When there is game breaking or ( simply can’t even create a hero on Europe ) bugs, it is no mystery how it happened.
BECAUSE CODE DOES NOT WRITE AND COMPILE AND INSTALL ITSELF.
When a bug happens all you have to do is look at the most recent changes you have made and there is your culprit.
Blizzard please fix your basic game problems.
Not always. Sometimes, bugs are like Hydra. Get rid of one, and two more takes its place.
I’d be interested in how they (Blizzard - not just the D3 team) handles CI/CD, Agile (Scrum or Kanban), automated unit testing, DevOps, etc.
I’ve seen a bug get reverted a few times. If I was West Coast, I’d apply for a job just to help them fix that business process problem.
Yes, when that happens you continue having set up breakpoints and study where the code breaks.
On and on this is what a coder does, and is how one fixes the bug and ensuing bugs found.
Breakpoints don’t help with detecting “did this break something else?”.
That’s where Unit Testing and User Acceptance Testing (UAT) come in. Automation helps ensure things PASS as they go from Dev to Test to Prod. This includes automating Deployments.
It is up to the managers to see:
I believe the problem is more likely that of a management/Business Process problem then a coder problem. But, that’s me.
No it doesn’t. Neither does the talent of the author that wrote it.
To correct you:
When coding in your C++ IDE you want to find where code crashes, so you set up ‘breakpoints’.
You then run the code and it stops at each break point where one may view the code itself and what it is interacting with.
This is how a coder finds the bugs.
What I wrote above is just the start of finding bugs.
You @DogBone are talking about finding bugs on client end.
I was talking about the Classic Game coders finding the bugs in the C++ IDE.
That is not how you ensure your fix did not break something in the (library of) code you aren’t even looking at.
Coders “find bugs” by looking at the Backlog.
They check to see if the bug is fixed by running the appropriate Unit Test. If the Unit Test passes, they hand it off for Code Review and/or check it in to The Code Repository (accordingto culture/protocol). What the programer doesn’t do (with breakpoints) is see if something somewhere else breaks. That is where automating Unit Testing (CI/CD, DevOps) comes in. Only then will they can see “dud my fix break something else”.
Of course, the larger team needs to ensure there are sufficient Unit Tests available. (Blizzard has had a lot job postings for this position).
Personally, breakpoints are the last ditch effort in debugging code. Appropriate Instrumentation of the code (logger) comes first.
Thanks Classic Team for fixing Europe ‘create hero’ error 316002
COOKIES DO NOT MIX AND BAKE THEMSELVES
But they should.
guess you don’t know THAT MUCH about programming/code work. lmao