Nope,sorry, it's the TESTERS fault if a buggy game is released, It's not a developer's job to create bug-free code (no such dev exists), but it IS the testers fault if buggy code is released. (I assume when you say "developers' you are referring to the individuals who actually create the code.)
Are you for real? That's cool tho. Next time I'll tell my employer it's all the testers fault and I'm not being paid to do a quality job.
Wonder how long I'll stay employed...
Yes I am for real. Code created by developers ain't perfect and it's not expected to be, which is why (where I work) there are several testers each of whom test various parts, including standalone (unit) and integrated.
developers often work on a specific piece of a whole, and as such are not usually familiar with what goes on in other parts. When their code is finally integrated into other parts, bugs quite often pop up. Other bugs are in reality mis-information imparted by those who write the requirements.
I've been a developer for almost 20 years, and I've NEVER worked for a company that penalized developers for creating bugs caught by testers, If any company did that, we'd run out of developers very quickly.Obviously if a given developer seems to be generating a LOT of bugs, then that obviously is an exception.
So your company punishes developers for bugs? Wow, let me know what company that is; I can't imagine any dev wanting to work there.
And BTW, when something is released into production, sometimes bugs happen, and in 99.9% of the cases the testers take the hit, assuming it wasn't something else like bad requirements.
It was more your wording which might have been a bit off initially. No offense meant. The deal is clear and it helped your argument to elaborate it.
Anyway about my company... more ex-company for good reason. Politics never do good if you got to take the beating opposite to proper management. You're right, noone likes to work for such.
Comments
Wonder how long I'll stay employed...
Yes I am for real. Code created by developers ain't perfect and it's not expected to be, which is why (where I work) there are several testers each of whom test various parts, including standalone (unit) and integrated.
developers often work on a specific piece of a whole, and as such are not usually familiar with what goes on in other parts. When their code is finally integrated into other parts, bugs quite often pop up. Other bugs are in reality mis-information imparted by those who write the requirements.
I've been a developer for almost 20 years, and I've NEVER worked for a company that penalized developers for creating bugs caught by testers, If any company did that, we'd run out of developers very quickly.Obviously if a given developer seems to be generating a LOT of bugs, then that obviously is an exception.
So your company punishes developers for bugs? Wow, let me know what company that is; I can't imagine any dev wanting to work there.
And BTW, when something is released into production, sometimes bugs happen, and in 99.9% of the cases the testers take the hit, assuming it wasn't something else like bad requirements.
It was more your wording which might have been a bit off initially. No offense meant. The deal is clear and it helped your argument to elaborate it.
Anyway about my company... more ex-company for good reason. Politics never do good if you got to take the beating opposite to proper management. You're right, noone likes to work for such.