Droid Engineer Archive
Thread: UPDATE -- there is no update ...
Thanks for the update. The fact that the Devs aren't giving you the courtesy of at least acknowledging your emails doesn't make me happy at all. If you end up surrendering your Correspondent position, at least you can be satisfied that you upheld YOUR end of the bargain
Please update us again if the situation changes. Thanks!
Stick with it!
Pain and perseverence and frustration will pay off in the end.
It's worth it. Just remember to drink alot tongiht to blow off some stress! (If it's legal for you to do so, that is).
Bulgaras wrote:Idea, anybody know the phone number for SOE customer support? How about Q or Holo's office/secretary? I'm more than willing to pay long distance charges to get a **edit** answer from the asshats.
I had some idiots flame me for thinking of doing the very same thing before. I actually called the support line.
I think we should flood their 800 support number today.
I am all for mad bumping all the posts on the main board that involve DE's. I think we should start putting most of our posts their or we should just take over another forum and make it ours, since our voice is not getting heard on out board.
Any ideas wich one we should just take over?
I am going to bump all the DE issuses I see on the main board that I can today. Boy I am glad my boss plays this game also, heheee
I feel for you Sin.
Normally, I'd defend the Devs, but they've gone well past the point of ridiculous now. We've waited, patiently(usually), and all of the other classes get immediate results and pages of communication. We don't get a **edit** thing.
So, yes, I say we now do whatever it takes to get a response. And I'm more than willing to vote with my dollar if that's what it takes to get them to address our issues for a change.
I'm going to go against the grain here and ask you to consider the other side for a minute. These guys are busy. Real busy. Keep in mind that for everything they tell us they fix they probably fix 20 other things silently. Nobody has just one job. No matter how big the company. Nobody works in a vaccuum. That's the nature of software.
Many of you do this for a living. I do. Put yourself in their place. It hasn't been very long. Consider the scope of issues they are dealing with. Understand that there are just so many hours in a day.
They aren't magicians, nor miracle workers. Some of you have experience with projects this size. If not, I do, and I'm telling you that it's unreasonable to expect at this point a perfect communication, fast and responsive all day to all people.
After a huge project releases like this, the devs minds do what I call a "gas out". They expel all the stress from the months of 7 day a week 14 hour days that occurred to get to launch. Give them a break.
It's too soon to judge whether they are good or bad based on the reality of the project and the time that has passed since release. We all want fixes. They do too. If you believe for one second that they don't care then you've never developed software. All developers attach to their code. They all want things to work. They all want things to be better.
Give these guys the benefit of the doubt for a change instead of making assumptions based on a too short timeline. They are people just like you.
Slythetove wrote:I'm going to go against the grain here and ask you to consider the other side for a minute. These guys are busy. Real busy. Keep in mind that for everything they tell us they fix they probably fix 20 other things silently. Nobody has just one job. No matter how big the company. Nobody works in a vaccuum. That's the nature of software.
Many of you do this for a living. I do. Put yourself in their place. It hasn't been very long. Consider the scope of issues they are dealing with. Understand that there are just so many hours in a day.
They aren't magicians, nor miracle workers. Some of you have experience with projects this size. If not, I do, and I'm telling you that it's unreasonable to expect at this point a perfect communication, fast and responsive all day to all people.
After a huge project releases like this, the devs minds do what I call a "gas out". They expel all the stress from the months of 7 day a week 14 hour days that occurred to get to launch. Give them a break.
It's too soon to judge whether they are good or bad based on the reality of the project and the time that has passed since release. We all want fixes. They do too. If you believe for one second that they don't care then you've never developed software. All developers attach to their code. They all want things to work. They all want things to be better.
Give these guys the benefit of the doubt for a change instead of making assumptions based on a too short timeline. They are people just like you.
At this poing, I don't think we're yelling for them to actually *fix* anything. We're so desperate all we want is some sort of feedback as to where we stand in their world. Are we "next month" do they "have no idea" what they're going to do to fix the class? Or is our class working just the way they want it to? We just want some basic communication. Furthermore, they aren't even responding to our Correspondents direct email. Even if they don't have the time to read the boards and respond, they could at least respond 1 time to the DE's correspondent knowing that she will then relay that information to us and make TONS of people happy. But they've choosent not to do that. Its just more insult to injury considering how much time they've spent writing long, well thought out posts in other profession's forums that are argueably already much better off than the DE class.
What I'm saying is that any reasonable person can assume they are not pleased with the class. They don't need to keep telling us that. They have asked us for ideas. Provide them.
There is no need to keep e-mailing the correspondant at this point saying "yes, we got your e-mail thanks".
I'm sorry I think they are within reasonable limits at this point still. Some of you are looking for changes or decisions too soon.