Debating opinions is bad communication

Two safe words in web development are “user error.” Something doesn’t work? Not my problem—it’s user error. And while this does happen, it’s also kind of a cop-out.

I have been the user in many “user error” stories, when a website feature did not work as I expected. I reported the issue to those who could fix it, and was told I was “doing it wrong” and my difficult was simply user error. When you’re having issues, being told you’re wrong isn’t helpful. Undercutting my experience as flawed isn’t a proper fix.
Continue reading →

“QA Will Give Me a Bug-free Website” and Other Lies We Tell Ourselves

If you work for a large corporation or on a project with limitless coffers, you have likely enjoyed working with a dedicated QA team. You build the website or oversee the coding efforts then hand off your labors to a separate team who systematically kicks the tires and identifies bugs with your work, reporting back on everything.

But, for the bulk of web work, QA and testing is not done by a standalone team with that single purpose. Rather, it’s one of many hats worn by everyone on a build team. Whether you’re a developer or a designer or a PM, everyone has a role in the QA process.

Continue reading →