<story><title>Testing is a separate skill and that’s why it can be frustrating</title><url>https://medium.com/planet-arkency/testing-is-a-separate-skill-and-thats-why-you-are-frustrated-7239b1500a6c#.s23ovtlo5</url></story><parent_chain></parent_chain><comment><author>koonsolo</author><text>The best testers that I know really enjoy breaking stuff. They have this special mission to break anything they get their hands on. They take great pride in finding the stuff that the developer probably didn&amp;#x27;t think of. They smile when it behaves weird, they laugh when it crashes. Their ego rises when they tell the developer that they were smarter.&lt;p&gt;And therefore, the one who built is, is not the person who makes it his lives mission to break it. Breaking it means more work, more searching for bugs, and then testing again. And nobody likes doing that. Except for awesome testers. They love looking at the face of a desperate developer getting frustrated by a nasty bug.</text></comment>
<story><title>Testing is a separate skill and that’s why it can be frustrating</title><url>https://medium.com/planet-arkency/testing-is-a-separate-skill-and-thats-why-you-are-frustrated-7239b1500a6c#.s23ovtlo5</url></story><parent_chain></parent_chain><comment><author>svantana</author><text>No doubt testing is a skill, and a very useful one, though I doubt this is the main frustration. Most people (at least myself) got into coding because they enjoy creating something from nothing. Maintaining and testing code is boring because it doesn&amp;#x27;t really do anything new, it&amp;#x27;s mostly fixing edge cases. Personally I try to make testing more creative by making ambitious testing tools (fuzzing, self-testing base classes, etc), which makes it more fun and therefore more likely to get done.</text></comment>