6 ms·
The last line is a little unfortunate. It made me think of: http://37signals.com/svn/posts/1528-the-bullshit-of-outage-language http://37signals.com/svn/posts/1
by paulbaumgart 15y ago
The last line is a little unfortunate. It made me think of: http://37signals.com/svn/posts/1528-the-bullshit-of-outage-language http://37signals.com/svn/posts/1528-the-bullshit-of-outage-l...
- panarky 15y agoContrast Microsoft's wishy washy "any inconvenience this may have caused" with Amazon's sincere apology. http://aws.amazon.com/message/65648/ http://aws.amazon.com/message/65648/ (Scroll to last paragraph.)
- Mythbusters 15y agoI was hoping to hear a little more technical apology from Microsoft. For a suit, reading what the VP posted might make sense, but for a techie like myself I really need to know that the platform is mature and stable. A detailed description of the problem helps me judge.
- screwt 15y agoTo be fair, the post does say they'll provide the technical explanation when they have more info: We will post an update on this situation, including details on the root cause analysis at the end of this incident. I think that's fair enough (assuming they don't just quietly forget about this last part).
- 4ad 15y agoSincere apology? You just told us to scroll to the last paragraph, presumably because most people who clicked your link would not have seen it. That's not a sincere apology, that's a huge wall of text that could have been about five times shorter. It's PR, it's always PR.
- abraham 15y agoIt isn't PR, it is a thorough technical rundown of the issue and what they are doing to improve it.
- 4ad 15y agoIt's verbose, not thorough, and it's light on the technical side. It only superficially looks technical to people who don't work in the field. Everything is PR. Even if this was indeed a very thorough and technical rundown of the issue, it would still exist only because of PR.
- lysium 15y agoAt least they didn't say "... may have caused".