Skip to main content

The Mythical Standard Build

Do your hear phrases like "All our users use [insert some technology]" spoken in your office? or possibly "We have a 'corporate standard' desktop". I have a lot. I have since my first job, back in the '90s. It's a commonly held belief in most of the client companies I've worked with. Programmers, testers, project managers and product owners frequently hold faith in the standard build.

It -is- a matter of faith. Often based on little more than wishful thinking or at best very loose 'standards'. The problem isn't purely one of client machines or end-users. I've often seen servers defined as 'clones' that in fact have quite different properties. e.g. different versions of java or application servers or even different time. The blind faith on these standard systems has caught myself and colleagues out so many times that I now find myself instantly questioning the assumption, and encouraging others to do the same. Even in this era of virtualisation, from experience, I can still safely say the Standard Build is a myth.

Lets take an example, the corporate PC. Customer sites often have a 'standard' desktop or note-book they hand out to new employees. Great, cloned or 'ghosted' from a central standard build. They have Standard Windows XP or Windows 7 etc. But how long does the PC's hardware stay the same? Sure it's all Dell or HP, with the same model number. But how often do Dell or HP (or example) update their chips/firmware/drivers...? How often do their external suppliers tweak a subsystem, if only to fix a bug? From my experience PC hardware changes frequently and that's at a level -I- can see, there's probably many more subtle changes under-the-hood that I'm missing.

But lets assume we've somehow managed to co-ordinate the Dell/Lenovo/HP/etc global supply chain to provide perfectly identical systems... What about where they are deployed? System 001 is being used in the USA, so it's got a US keyboard, US power supply and is configured with locale and date settings for the USA. System 002 is in France, has a French keyboard, power supply and is configured with French locale and date settings. Also of course, there's the Spanish, UK and did I mention the new Hong Kong office?

Think about how these systems are deployed. It's unlikely they'll be rolled out overnight. They've probably been deployed over at least several weeks, and probably months and years. So we hit our first issue: Each site is probably using a different version of various pieces of hardware and operating system software. Furthermore, the offices themselves probably contain different hardware etc. Over time, as new people arrived, new hardware was purchased or repurposed to get them up and running.

We've still yet to consider the everyday usage of the systems. They each have, for example, Windows 7 installed. But Microsoft Windows is routinely patched, sorry 'updated' with new software. The patches are unlikely to hit all the systems at the same time for several reasons including different regional-deployment schedules and individual system usage. If a user rarely restarts their system, it could be a while before updates get installed. I'll labour the point and mention the anti-virus system, Microsoft Office, and browser plugins as more examples of software on rolling updates.

Real users 'tweak' their computers. They configure their systems to suit them. Computers are designed that way, each user can setup their desktop how they want. In fact they may well be encouraged - to switch to an ergonomic keyboard for example. They may need to increase the font size, or change the screen-resolution. And what's more, they kept getting this annoying warning message in their 'Internet browser' every time they visited their favourite web-site - so they 'fixed' that in the preferences panel.

You get the picture. The standard is at best a guideline or goal, and at worst a dangerous simplification. When people talk of a standard desktop, server or 'client' think like a tester and question "What standard is it?" and "How standard is it?" As a tester those 30% of users who don't have a 'Euro' key on their keyboard [that's easy to find] might do things a little differently. Or maybe the new desktop-support lead in the New York office has enabled all the windows-firewalls on the desktop systems, hows your application going to handle that?

Comments

  1. Excellent analysis as always. Worth pointing out that the machines that usually deviate furthest from the 'standard build' are the ones the developers themselves are using to write the software. These tend to be higher spec and often have local admin rights. Developers will therefore usually have the latest updates, newest browser versions and so forth. We then wonder why the stuff we build doesn't work right when used by our production users!

    ReplyDelete

Post a Comment

Popular posts from this blog

Why you might need testers

I remember teaching my son to ride his bike. No, Strike that, Helping him to learn to ride his bike. It’s that way round – if we are honest – he was changing his brain so it could adapt to the mechanism and behaviour of the bike. I was just holding the bike, pushing and showering him with praise and tips.
If he fell, I didn’t and couldn’t change the way he was riding the bike. I suggested things, rubbed his sore knee and pointed out that he had just cycled more in that last attempt – than he had ever managed before - Son this is working, you’re getting it.
I had help of course, Gravity being one. When he lost balance, it hurt. Not a lot, but enough for his brain to get the feedback it needed to rewire a few neurons. If the mistakes were subtler, advice might help – try going faster – that will make the bike less wobbly. The excitement of going faster and better helped rewire a few more neurons.
When we have this sort of immediate feedback we learn quicker, we improve our game. When the f…

Thank you for finding the bug I missed.

Thank you to the colleague/customer/product owner, who found the bug I missed. That oversight, was (at least in part) my mistake. I've been thinking about what happened and what that means to me and my team.

I'm happy you told me about the issue you found, because you...

1) Opened my eyes to a situation I'd never have thought to investigate.

2) Gave me another item for my checklist of things to check in future.

3) Made me remember, that we are never done testing.

4) Are never sure if the application 'works' well enough.

5) Reminded me to explore more and build less.

6) To request that we may wish to assign more time to finding these issues.

7) Let me experience the hindsight bias, so that the edge-case now seems obvious!

Google Maps Queue Jumps.

Google Maps directs me to and from my client sites. I've saved the location of the client's car parks, when I start the app in the morning - it knows where I want to go. When I start it at the end of the day, Google knows where I want to go.
This is great! It guides me around traffic jams, adjusts when I miss a turn and even offers faster routes en-route as they become available.
But sometimes Google Maps does something wrong. I don't mean incorrect, like how it sometimes gets a street name wrong (typically in a rural area). I don't mean how its GPS fix might put me in a neighbouring street (10m to my left - when there are trees overhead).
I mean wrong - As in something unfair and socially unacceptable. An action, that if a person did it, would be frowned upon.
Example:
Let’s assume a road has a traffic jam, so instead of the cars doing around 60 mph, we are crawling at <10 mph.
In the middle of this traffic jam, the road has a junction, an example is shown here: