Defects to Errors
Samar: Oh God! Why did you pass on this DEFECT to us!!
QA Audit, I don’t think there is anything more dreadful for a Software Engineer. They try their best to ensure that there are any defects or errors found by the Auditor, but auditor is auditor, he will do anything to find out a defect and then use it against you. After every audit the auditor will eat your brain for minimum 15 minutes explaining what is a difference between a defect and an error.
Co’mon man! does that make anything better or worse by calling a defect an error? I think these terms have been devised by these vicious auditors to ensure that their importance is there in the team and they can show their power.
I have seen that the Software Engineer is the only person who does not have any power or say – requirement is sent by customer, team is decided by manager, design and documents are made by TL, discussion with client is done by TL, then audit is done by QA and at last the appraisal is done by Manager. So all powerful works are with others, the Software Engineer or better call him “Bloody Coder” is required to understand the illogical design made by the TL and then ask him to change the design because of several number of problems which the TL did not think of, then do all coding and commenting, if a bug is found by the testing team or client all blame on his coding skills, after this audit sessions to be attended by this Bloody Coder. So overall the most ridiculous work in a team in a Software Company is done by the Bloody Coder yet no say of him and no respite for him.
See how big mouthed these QA people are.