Satyn wrote:tbh i dont understand whats so important about knowing the details about what went wrong. Things went wrong, apparently very serious and it should be sorted right now. Thats all I need to know.
It's not so much a matter of needing to know as wanting to know. Many of us with technical backgrounds or professions (or others still who just like to think they do) are having a hard time getting our heads around just why this 'solution' is the one GOA decided to use and more information might help restore our confidence in their systems.
Bad analogy - you've leased a car and you get it serviced by the company from whom you are leasing it. Then it stops working one day, so the company takes it in to service it. You get it back a week later but it has a funny noise in the engine. The company says they can't do anything about it. If you don't know anything about cars, you'll be annoyed but happy to have the car back. But if you're a mechanic, you'll be curious what the company did to fix it, and especially why there's still the funny noise, as maybe you've fixed cars before and managed to do so without the noise.
Basically we've been given back the server but with the obvious problem of missing items. Some of us want to know in more detail why that problem was left uncorrected. With GOA not telling us, it (further) reduces our confidence in how they run their systems.
That said, when I worked in e-commerce, we'd never release any sort of internal system details to anyone outside the company. As you said, no one
needs to know, and if you release some information if just makes (some) people want to know more and more about how things work. So while I'd personally like to know what happened, I can see perfectly well why they are unlikely to share that information.
)
