Software Testing

Ever since I got an iPhone 5S, I have been enamored with Apple products. The fit and finish, and ergonomics seems to be well thought out.

Heard about the new iOS 13 and I “upgraded” it for my SE the first hours it was available.

Now my reminder app, which I relied upon so heavily, is in shambles.

Over the years it has amazed me at how little so much software seems to have been tested before public release.  And in many instances, that which has been sufficiently tested was not used in the “real world” by the people actually needing it, but some programmer’s idea of how things should be.

Heck, look at the mess involving the 737 Max. Not much thought was put into the “what if’s”.

I think we can all relate to software like that.

The GPS navigation system in my Mercedes is so clunky and has so many steps I have found it easier just to use the iPhone.

If there was one complaint my employers had during my professional programming career it was that I was too slow in releasing  it. But I am proud to say I had very few returns from “buggy” software.

My friend the programming guru would always take as much time writing sub programs to test his software as he did actual coding in the software itself. He easily spent 50%-50% between testing and production software.

In Apple’s defense while they have “beta” testers it’s one thing to be testing internally and another to suddenly have millions using it finding ways to induce errors the testers couldn’t do.

But in my case….on my iPhone SE, the reminder app is now brain dead. Reminders from 2018  that I thought it had deleted (and why didn’t it?) when acknowledged are coming back from a year ago. All they had to do was install this software on one of the less than a dozen eligible phone models and run simple tests.

Sure is a lot of software crap out there.

Think I’ll take the advice of so many Lexicans on the F/B page and now wait at least a week, or wait until version “.1” comes out.



Filed under Other Stuff, Uncategorized

2 responses to “Software Testing

  1. Pingback: Technological Waves and Business | The Lexicans

  2. Back when the microcomputer industry was in its infancy, and I was active, system software was problematic. Much of it we had to write ourselves, and getting a BIOS up and running could be, shall we say, rather interesting. back then, you had to be an 8080/Z80 assembly language programmer.

    Promises were made, such as Microsoft’s promise of the complex data type for their FORTRAN compiler, which never materialized. promises of software that didn’t materialize led to coining the term “ghostware.”

    Documentation was even worse. Even well into the 80s. At one conference, the speaker asked everyone who was a technical writer to raise their hand. He then told them they were the armpit of the industry.

    Things haven’t changed much.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s