So your story is that you called people names and got fired?
Also, he didn't do his job.
Anyway, I think the worst is probably bugs filed by devs. So often, a dev will file a bug because they found a problem, they'll fix the problem, and then the bug will be resolved and assigned to QA to close.
But since the dev already knew exactly what was causing the bug and why, you're lucky to have any repro steps. They already know, why would they bother writing it down for themselves?
So QA gets the bug, and you have no way to tell if it's been fixed. You can look at the code, and see that the change they said needed to be made was in fact made. But you can't understand their esoteric description, and have no idea how to prove the problem has been fixed.
I will take a dozen devs bouncing a bug back as no repro because they screwed up the steps over one badly written resolved bug filed by a dev.
you're = you are
your = belonging to you
their = belonging to them
there = not here
they're = they are
0
FramlingFaceHeadGeebs has bad ideas.Registered Userregular
edited September 2011
And I'll also note, I very rarely have any of these problems on my current team. We actually have a really healthy relationship between our devs and our testers.
Framling on
you're = you are
your = belonging to you
their = belonging to them
there = not here
they're = they are
0
MichaelLCIn what furnace was thy brain?ChicagoRegistered Userregular
So your story is that you called people names and got fired?
It's all about the context. You see that it's the other side of the Trenches story, right?
Also Henroid said nobody was fired, so wanted to offer an alternative possibility.
I can see that you tried to make it the other side of the story, except you apparently ignored the testers waiting a few builds, and devs throwing controllers and being huge douches for four days, and the dev admitting he hadn't bothered following the repro steps, presumably all for the sake of fitting it all into your little narrative.
But no, you're right, those testers have totally got it too easy.
you're = you are
your = belonging to you
their = belonging to them
there = not here
they're = they are
0
MichaelLCIn what furnace was thy brain?ChicagoRegistered Userregular
So your story is that you called people names and got fired?
It's all about the context. You see that it's the other side of the Trenches story, right?
Also Henroid said nobody was fired, so wanted to offer an alternative possibility.
I can see that you tried to make it the other side of the story, except you apparently ignored the testers waiting a few builds, and devs throwing controllers and being huge douches for four days, and the dev admitting he hadn't bothered following the repro steps, presumably all for the sake of fitting it all into your little narrative.
But no, you're right, those testers have totally got it too easy.
Wow... seem to be taking a one-off amusement a little too seriously.
But to reply, how do we know the OP's story is the absolute truth? They never said the Dev he was having trouble with came down until he demo'd it for the Dev. Maybe those other guys were being gooses unknown to the original Dev.
Just making a comment on how we never really get the whole story - either here from an anonymous writer, or anywhere else.
the only thing that confuses me is the part about "starting without armor (shields)", because in halo you always have them by default. It would be silly for a halo dev to assume a no-shields start as the norm.
I always enjoyed finding bugs that required weird/lucky timing to get right. Like pausing the game right when a room loads or skipping a cutscene the second a certain animation plays.
0
Dark Raven XLaugh hard, run fast,be kindRegistered Userregular
the only thing that confuses me is the part about "starting without armor (shields)", because in halo you always have them by default. It would be silly for a halo dev to assume a no-shields start as the norm.
Since they're making the game, they have the option to turn em off, to get to the kill faster. That's what the issue was; the dev switching the shields off to try and repro the bug quicker. :P
the only thing that confuses me is the part about "starting without armor (shields)", because in halo you always have them by default. It would be silly for a halo dev to assume a no-shields start as the norm.
Not necessarily. There are a few gametypes in Halo that don't have shields, but even so this is an issue more of the dev assuming that the bug would operate the same without shields on spawn and trying to take a shortcut even when QA knew better and told him so.
@vgreminders - Don't miss out on timed events in gaming! @gamefacts - Totally and utterly true gaming facts on the regular!
Posts
Also, he didn't do his job.
Anyway, I think the worst is probably bugs filed by devs. So often, a dev will file a bug because they found a problem, they'll fix the problem, and then the bug will be resolved and assigned to QA to close.
But since the dev already knew exactly what was causing the bug and why, you're lucky to have any repro steps. They already know, why would they bother writing it down for themselves?
So QA gets the bug, and you have no way to tell if it's been fixed. You can look at the code, and see that the change they said needed to be made was in fact made. But you can't understand their esoteric description, and have no idea how to prove the problem has been fixed.
I will take a dozen devs bouncing a bug back as no repro because they screwed up the steps over one badly written resolved bug filed by a dev.
your = belonging to you
their = belonging to them
there = not here
they're = they are
your = belonging to you
their = belonging to them
there = not here
they're = they are
It's all about the context. You see that it's the other side of the Trenches story, right?
Also Henroid said nobody was fired, so wanted to offer an alternative possibility.
I can see that you tried to make it the other side of the story, except you apparently ignored the testers waiting a few builds, and devs throwing controllers and being huge douches for four days, and the dev admitting he hadn't bothered following the repro steps, presumably all for the sake of fitting it all into your little narrative.
But no, you're right, those testers have totally got it too easy.
your = belonging to you
their = belonging to them
there = not here
they're = they are
Wow... seem to be taking a one-off amusement a little too seriously.
But to reply, how do we know the OP's story is the absolute truth? They never said the Dev he was having trouble with came down until he demo'd it for the Dev. Maybe those other guys were being gooses unknown to the original Dev.
Just making a comment on how we never really get the whole story - either here from an anonymous writer, or anywhere else.
(If they are, they never fixed it)
the only thing that confuses me is the part about "starting without armor (shields)", because in halo you always have them by default. It would be silly for a halo dev to assume a no-shields start as the norm.
Since they're making the game, they have the option to turn em off, to get to the kill faster. That's what the issue was; the dev switching the shields off to try and repro the bug quicker. :P
Not necessarily. There are a few gametypes in Halo that don't have shields, but even so this is an issue more of the dev assuming that the bug would operate the same without shields on spawn and trying to take a shortcut even when QA knew better and told him so.
@gamefacts - Totally and utterly true gaming facts on the regular!