Too Long; Didn't Read
As developers, we <em>love</em> to <em>hate</em> on QAs. I’m just kidding, of course. I <em>love</em> my QA. I <em>love</em> that they find bugs in my team’s code. It’s my favourite part of the <strong>agile waterfall</strong> development that we have. But, in all seriousness, let’s talk about a QA’s (<strong>Quality Assurance</strong>) role in your development team. Do you even have one on your development team? If you don’t, why not? Do you actually <em>need</em> one? Let’s dissect a little.