‘The Internet Explorer Effect’ In Bugged Releases

You are here


Internet Explorer BuggedOne unlucky day a new software update was released. A humongous refactoring thing has caused the team to miss three bugs. Only three. It’s not like it is possible to get a 100% bugles release done, right? And still that part was the exact part where weird stuff started going on.

The weird stuff

The weird stuff, as mentioned above began shortly after the release. With the user reports on the mentioned three bugs some other reports started to come in. Like reports on the functionality that was always there, always! Users, after smelling some blood became absolutely prejudiced to the entire product. It’s like they were blinded with a desperate need of finding and reporting a bug. Thus they were actually demanding patches on the things that were always there. Weird, right?

But it was there all the time?!  

It seems like the shock caused by the three original bugs has indeed created a butterfly effect. Users being desperate on proving their superior knowledge are racing to report something in a better than their predecessors way. They do not care of the previous functionality now, it’s about self-esteem (pure internet psychology) to them. The same has ruined the Internet Explorer. I know you will be tossing tomatoes at me after these words but the latest versions of IE are pretty much OK. It’s all about its image and the legacy burden it is carrying for years, and not about functionality nowadays.  

Now more stuff needs to be patched and more additional work to do, because of mere three bugs. Why’d that happen? There are two major reasons:

  • It’s a historical legacy burden. IT has indeed acted like ‘clowns’ as some users would say while releasing way too bugged software over and over. Thus we have a lousy reputation and users are expecting to find several issues. More than that, they are even encouraged to do so.
  • Agile sound too god to be true. And the business sides tends to take all that as a clear coin. Thus the business side is not too much into spending budget on QA. No bugs are now being delivered by developers, right? And you know what they say “a cheap man pays twice the price”.