@AC Typical programmer response → #
Posted Friday 17th July 2009 11:18 GMT
In Reg readers crack case of the $23 quadrillion overcharge
"So the AC in the article asserts that it's QA's fault for not finding the bug, typical programmer, using QA as a safety net for shoddy code."
Not all of us blame QA... but then again what should organizations expect when they expect code to be completed *yesterday*
True, QA should have picked up on the issue, but so should have the developer. Everyone seems so quick to point the finger at others nowadays. Some bugs just go unnoticed... look at VMWare some months ago when they left an date check statement in an update rendering entire virtualisation environments useless. Even the biggest development houses make mistakes.
Sorry might have got the wrong end of the stick so feel free to flame away. :-)
