Why don't software geeks test software updates?

[k0ua]

Scenario:.. "honey all of my Kindle books on my android device are gone!" says the wife.

Of course this is my problem to repair, as she has given it her best shot.

Resolution: After rolling back, de-registration and re-registration twice. I have come to the conclusion that the latest software update to the Kindle application on the android no longer works. This seems to be borne out by reading the Google play discussion forum for this app.. Probably millions of loyal Amazon Kindle users cannot read their payed for content on their devices after this automatic software update. Isn't that great? Software geeks release a software update without any testing to actually see if it works? I am sick of this.. I set the device to no longer do automatic software updates. It seems every other day or two some stupid software update either blows up the application the update is targeted to or actually ruins a totally innocent application. Like Google play music updates blows up your voice commands app on your android phone.. Isn't that grand? Software developers are idiots!

Anyway, Rant off I guess, and I can get glad in the same pant's I got mad in. Thanks for listening.

James K0UA

 

[rekees4300]

There's nothing more frustrating than a security update that does more damage than it was suppose to prevent.

 

[Katahdin]

I work in IT on the systems administrator side, we got a chuckle out of this one.

Hard to really say without knowing all the circumstances. Could be the software developer or QA person is sloppy. Might also be the developer didn't have access to your customer data to test against it due to privacy controls, or something was setup differently on the test system. I'm sure if enough Kindle users complain there will be plenty of finger pointing and postmortem meetings. Sh*t Happens on computers too, the best you can do is learn from the mistakes, make sure the problem doesn't happen again, and move on.

 

[k0ua]

View attachment 351891

I work in IT on the systems administrator side, we got a chuckle out of this one.

Hard to really say without knowing all the circumstances. Could be the software developer or QA person is sloppy. Might also be the developer didn't have access to your customer data to test against it due to privacy controls, or something was setup differently on the test system. I'm sure if enough Kindle users complain there will be plenty of finger pointing and postmortem meetings. Sh*t Happens on computers too, the best you can do is learn from the mistakes, make sure the problem doesn't happen again, and move on.

I think the humorous poster says it all. This seems to be almost a daily occurrence for the android apps.

 

[phiferpharm]

Well James, just remember.. to err is human... to really screw up takes a computer program.

 

[k0ua]

Well James, just remember.. to err is human... to really screw up takes a computer program.

Roger that!

 

[s219]

Android is like the Wild West of software development. Not enough standardization and zillions of different devices. Plus OS versions are all over the place (many devices ship with an OS over 2 years old and never get updates). It's a bear to QA on. My guess is that they tested it on the top 10-20 devices only, which is common practice on Android.

 

[k0ua]

Android is like the Wild West of software development. Not enough standardization and zillions of different devices. Plus OS versions are all over the place (many devices ship with an OS over 2 years old and never get updates). It's a bear to QA on. My guess is that they tested it on the top 10-20 devices only, which is common practice on Android.

Ok, but wouldn't a Motorola Droid Razr-M be in the top tier of common machines? I would think so.

 

[WM75Guy]

I love the three stock answers you get from software programmers: #1 - It's a "known issue", their code for "It's broke, we know it's broke, but we don't know how to fix it", #2 - "That's going to be fixed in a future upgrade. No sir, not the next upgrade, a future upgrade", and the all time favorite #3 - "There's nothing wrong with the software, it's due to user error".

 

[aczlan]

I love the three stock answers you get from software programmers: #1 - It's a "known issue", their code for "It's broke, we know it's broke, but we don't know how to fix it", #2 - "That's going to be fixed in a future upgrade. No sir, not the next upgrade, a future upgrade", and the all time favorite #3 - "There's nothing wrong with the software, it's due to user error".

There is also #4, Sales sold the customer on having the software by date X with Y features without consulting Development, then Management wouldn't let Development change the release date or add extra people to get it out and working on time...

Aaron Z