> In my opinion, a programmer must write a good code. And leave the testing to the QA. Aside from the "not my problem" vibe that gives off, I strongly disagree

> In my opinion, a programmer must write a good code. And leave the testing to the QA. Aside from the "not my problem" vibe that gives off, I strongly disagree. QA is helpful for covering weird user interactions and writing tests against bugs discovered in production, but you as the programmer should know what your code is supposed to do while you're writing it. Best write tests then rather than six months later when you've forgotten what it was for.