Rajesh wrote: >From my perception it depends on how much interest you have on the job. If you >have interest then surely you will do an excellent job. As a developer i >prefer to be in development. And hates Quality team who always finds mistakes >on what i did, to justify their work.
Thanks and Regards Rajesh G //-------------------------------------------------------------------------------------------------------------------------- Part of QA's job is to find mistakes. Their view is "Zero flaws = good product." They also have (or should have) a set of (sometimes written) guidelines by which they consistently follow that gets code into that final "good product" state. Each person should consistently try to improve themselves and assume they aren't perfect. No one likes having their mistakes pointed out to them and programmers are especially LAZY when it comes to fixing their code. What I do is take the mistakes that get pointed out to me, initially balk at the idea I did something wrong, then immediately switch gears and think maybe I did something wrong, then I attempt to go fix whatever is wrong (which inevitably breaks two more things). Wash, rinse, repeat. It is a work in progress to eliminate the "balking" phase. In this case, have you tried joyfully fixing the "mistakes" instead of complaining about it? Mistakes are inevitable - programmers see the trees, QA should be viewing the forest. Plus you have to work with these people. And they ARE people after all. And they are trying to work with you too. -- Thomas Hruska CubicleSoft President //---------------------------------------------------------------------------------------------------------------------------- I'm in agreement here. I go way out of my way to make sure my code doesn't have a bug. It might seem a waste of time, but what I do is whenever I write a new function, is I compile and run to see if I can find any problems. If it's broken, it usually takes me five to thirty minutes to make sure it's fixed. if it still gets kicked back from my Testers, then I have a good clue as to where the problem might be at. Michael [Non-text portions of this message have been removed]
