> Having dedicated QA is not always good. In fact it is often counter-productive. Maybe 'dedicated QA' is a bad but a developer must at least be point man for

> Having dedicated QA is not always good. In fact it is often counter-productive. Maybe 'dedicated QA' is a bad but a developer must at least be point man for test, even if the responsibilities aren't 100% of their workload. One could argue that having a horde of peons to click randomly is counter-productive, but teams >6 or so need a specific dev responsible for automating test. Its too specific a domain, and intermittently demanding, and to force all devs to split the duties.