Community Relations Archive
Thread: Thanks, JustG for the excellent communication about this morning's problems. Keep it up!
Page 1 of 2
DeQuosaek
Tue Jan 25, 2005 4:07 pm
#1
Like the subject says, I thinkthe clear description of the problems that were faced this morning is exactly the way things should be done. It was great to see the explanation communicated to us and now we have an idea of what happened and how the team sprang into action to fix it as soon as it was diagnosed.
That is what I consider great community relations! Keep up the good work. 
Gouta
Tue Jan 25, 2005 5:07 pm
#2
I agree, 2005 so far has seen far better communication from the developers.
Calandryll_SOE
Tue Jan 25, 2005 5:10 pm
#3
Glad you think so! Of course, it's our primary goal to avoid problems like this in the first place, but when they occur we will do our best to update you.
omadnay
Tue Jan 25, 2005 5:58 pm
#4
Yeah, the Postmortem Post was a nice read.
It's really great to get that information out there. It helps to paint a clear picture of what kind of work and procedures are involved in snafu's like this.
As with all technology, the users of it rarely think anything more of it than turning it on and off by pushing buttons.
Well, doing the crunching to find the sollutions and create the new build in 4.5 hours is a clearer indication of the efforts involved, as opposed to the concepts of simply replacing a grumpy hampster. (Although they can bite and that could chew up a good amount of time... pun not intended, but left because I never intended this post to have so many words)
Bottom line... you learn something new every day and sometimes it's nice to hear in detail what other people learned through their problems.
Thanks for the info.
- Omadda Szool
Kauri
It's really great to get that information out there. It helps to paint a clear picture of what kind of work and procedures are involved in snafu's like this.
As with all technology, the users of it rarely think anything more of it than turning it on and off by pushing buttons.
Well, doing the crunching to find the sollutions and create the new build in 4.5 hours is a clearer indication of the efforts involved, as opposed to the concepts of simply replacing a grumpy hampster. (Although they can bite and that could chew up a good amount of time... pun not intended, but left because I never intended this post to have so many words)
Bottom line... you learn something new every day and sometimes it's nice to hear in detail what other people learned through their problems.
Thanks for the info.
- Omadda Szool
Kauri
Mirkwoods
Tue Jan 25, 2005 6:32 pm
#5
I completely agree. Nice of you to let us in on what the problems were.
Please continue this policy.
Maybe in the future, you could post some pictures of the hampsters and give us like some of their likes and dislikes.
I think we need to have an in-game hampster wheel. That would be funny.
WiskeDarkmoon
Tue Jan 25, 2005 8:12 pm
#6
Tell the truth, the hamster handler was late with feeding this morning
Seriously though this is the the kind of communication that we need. Technology is a bugger sometimes, knowing what happened makes the players alot more understanding.
Seriously though this is the the kind of communication that we need. Technology is a bugger sometimes, knowing what happened makes the players alot more understanding.
BenkeiHami
Tue Jan 25, 2005 8:19 pm
#7
indeed, I hope you can continue to give a post mortem when thing go wrong...go wrong....go wrong /bonk 
Bacacuba
Tue Jan 25, 2005 10:13 pm
#8
I'll chime in and say that the communication from the development team has nearly hit an 'A' level in my book and is rapidly approching it. The explaination of what happened today is exactly the type of information we've been needing from the team from day 1. Not everyone out there has worked with huge server clusters and pushing publishes or releases to these types of machines and often just don't understand the undertaking it is. And more so some of us who have often think we know better than those with their hands on the keyboard at SOE. *points at self on that one* There are checklists and plans of action when things go wrong. Honestly I can't say things could have been handled much better than they were. Two Thumbs Up.
-- Rayck
twiafu
Wed Jan 26, 2005 12:15 am
#9
DeQuosaek wrote:
Like the subject says, I thinkthe clear description of the problems that were faced this morning is exactly the way things should be done. It was great to see the explanation communicated to us and now we have an idea of what happened and how the team sprang into action to fix it as soon as it was diagnosed.
That is what I consider great community relations! Keep up the good work.
Could not have said it any better!
Leviathan81
Wed Jan 26, 2005 2:45 am
#10
I too appreciated the postmortem-post, but honestly: The second you realized you had to do a new build and stuff, you must have known it would take a long time.
Would it have been that hard to post something like: "Downtime is going to take at least 3 hours" so people knew they didn't have to wait?
Considering the posts on some of the galaxy-boards, people have been waiting for hours for the servers to get up again, if we had known it would take that long, we could have done something else...
Now please don't take this as a rant, I just wanted to show that there is still room for improvement in the communication.
Would it have been that hard to post something like: "Downtime is going to take at least 3 hours" so people knew they didn't have to wait?
Considering the posts on some of the galaxy-boards, people have been waiting for hours for the servers to get up again, if we had known it would take that long, we could have done something else...
Now please don't take this as a rant, I just wanted to show that there is still room for improvement in the communication.
DeQuosaek
Wed Jan 26, 2005 9:27 am
#12
Leviathan81 wrote:
I too appreciated the postmortem-post, but honestly: The second you realized you had to do a new build and stuff, you must have known it would take a long time.
Would it have been that hard to post something like: "Downtime is going to take at least 3 hours" so people knew they didn't have to wait?
Leviathan81
Wed Jan 26, 2005 9:40 am
#13
DeQuosaek wrote:
Yeah, well, "no ETA" sure is awesome information, but you can't tell me they don't know how long doing a new build and distributing it takes.
So either most of those 4.5 hours were actually spent diagnosing the problem (in which case I didn't say anything) or they knew more than they told us by that time.
Page 1 of 2