Date: 2009-04-15 03:07 pm (UTC)
the_axel: (Default)
From: [personal profile] the_axel
I agree with [livejournal.com profile] apestyle.

That's one of the two scenario's that makes sense to me.

Code monkey does something dumb and changes the production environment without adequate testing and something blows up. My understanding is that Amazon's website doesn't have one central group that owns it but is made up of many modules each with it's own group.

The other is that some anti-gay hacker or troll found a weakness in their system and exploited it. The fact that this exploded over a long weekend, and a Christian holiday at that, lends credence to that theory.

One of the things that supports it not being planned is that not all versions of a given product were impacted. When this story broke I looked at a couple of the impacted titles and found that some had lost their Sales rank, and others didn't. If Amazon had planned this I think they would have been a lot more comprehensive.

The initial responses that went out were likely from a customer service centre in India who have a limited number of form e-mails to respond with rather than being a thought out & planned answer.

http://blogs.itworldcanada.com/shane/2009/04/14/what-amazons-catalogue-glitch-says-about-cloud-based-metadata/

http://www.thestar.com/unassigned/article/617982

P.S. Are you still playing Warhammer Online?
This account has disabled anonymous posting.
If you don't have an account you can create one now.
HTML doesn't work in the subject.
More info about formatting

Profile

razorjak: (Default)
BrickJAK

July 2017

S M T W T F S
      1
2345678
9101112131415
16171819202122
23242526 272829
3031     

Style Credit

Expand Cut Tags

No cut tags
Page generated Jun. 25th, 2025 12:30 pm
Powered by Dreamwidth Studios