The clean hands strategy

Testers can be a great bug inside the developer's head .Vis-versa is also true ,there is no reason why people should lose their friendship because of code .The code needs to be regarded as a separate entity that doesn't belong to the developer.The dev has to tell the tester ,"Man this code has its own personality ,its like an artificial intelligence thing you know ".This is the first step because testers think the developers are doing it on purpose ,like they know the problem but don't think right because regression is always there.Or because the dev is a lazy coke addict .

Devs also have a paradigm about testers ,they think testers are always seeking to find their bugs not only in code which some devs consider their property but in the dev himself .They think the tester is a spoiled brat who nags about the existence of a red asterisk or a stylish title in the middle of the night,not knowing the amount of hard work that was necessary for more important stuff .Some testers would say "man I don't know how this happened but I just went to the bathroom and came back ,clicked on the button and boom ".Now try to trace THAT.

Nobody is wrong really ,its just that both have a different experience of the world ,one is trying to be God and the other is saying why is God punishing me.So There really needs to be a shared language between the two ,a special language from which both can understand one another and dis identify with the app.

I thought the dev can just write his tests, test them and after they work just send them to the tester ,so the tester knows the dev has clean hands and isn't responsible for any rash behavior outside of his testing habitat.The tester can then try out regression tests ,and send the dev the tests he would like him to test ,that he intuitively knows would backfire ,you can call it the clean hands strategy .