Archive for the ‘Maxims’ Category

QA Career Advice from Barron’s

Tuesday, February 16th, 2016 by The Director

Last week’s Barron’s had an article that pretty much covers the best way to enjoy a long career in QA.

Backward Compatibility, Explained

Tuesday, January 22nd, 2013 by The Director

Troy Hunt has a long post on how many desktops are still running Internet Explorer 8 on Windows XP and why that is.

If you’ve read this blog for much of its five year existence, you know I harp a lot on understanding why so many users are locked into old browsers, and why the number of them still running old versions of IE is still quite high. And why you need to account for it, whether to make your stuff backward compatible or to consciously decide not to support old beasts out there and what that might mean.

Also, you should always find out what your clients are running. Oh, the number of times developers, left to their own devices, would write things for their clients that their clients would be unable to run.

(Link via tweet.)

Borrowed Maxim

Wednesday, December 31st, 2008 by The Director

From a post by Michele Smith:

A good plan, violently executed now, is better than a perfect plan next week. (General George Patton)

As a reminder, in QA you get style points if you actually shell-shock a dev team.

Axiomatic != Automatic

Tuesday, December 23rd, 2008 by The Director

I only state the obvious because it’s often ignored: Trusting the developers is not a quality assurance process.

A Maxim From The Original Latin

Monday, November 10th, 2008 by The Director

The physicians’ first rule: Primum non nocere.  First, do no harm.  Silly physicians

QA’s first rule:  Primum nocere.  Quondam res est vulnero, tentatio iterum.  First, do harm.  Then, when the application is down, hit it again.

(No free Internet Latin translators were harmed in the creation of this  maxim; however, the same cannot be said to those instructors or speakers of Latin who might read it and suffer.)

wordpress visitors