“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.


Estimate It Live

Often during a client meeting, there are times when a defined scope of work is hypothetically augmented by a simple “could it do this?” or “can it do that?” comment. Invariably, the answer to such inquiries is a “yes” followed by an immediate “but” (#newbandname #immediatebut). Unless the request is fully impossible—e.g. Can this website teleport me to a bouncy house containing a million fat-free-but-still-good-tasting all-beef cheeseburgers served on levitating golden plates of pure love?—with infinite time and budget, nearly anything is possible on the web.


What Is a CDN? A Simple Visual Explanation

A CDN (Content Delivery Network) is becoming more and more commonplace in hosting plan offerings and a must for an business site. By hosting web content on servers that are spread across the globe, you can deliver content to any user faster by targeting servers that are relatively more local to them.

But if you’re like me, you are not overly technical; you get the concept of a CDN in theory, but do you GET IT get it? Here’s my nontechnical take on what a CDN is and why it’s a true benefit for any website.