Droid Engineer Archive

Well, if they didn't work on the problem yesterday, then it's likely they aren't working on Sunday, and won't work on the problem until Monday, at the earliest. This means that the next Hot Fix won't be until Tuesday morning. In the meantime, we can't sell droids for 3 days!

What bothers me is their Testing and Debugging Methodology. In this case, it is elementary that Hot Fixes should not be done on Saturday Morning unless they are absolutely necessary. I'm a developer for a small company with 200 people. There is NO WAY we would change software on Friday afternoon, unless we were prepared to work on it on Saturday. We know better, and the developers of SWG should know better, as well.

The other thing that bothers me is the way they test:

1) Their programmers do not test their changes; they simply push them out. Many of these problems are such that the simplest test would discovery them. Anytime a programmer changes code, he needs to do elementary testing on that code, and I don't think these guys do that.

2) They roll code from the Test Server to the Live Servers without carefully reading the reports from those customers who are loyal enough to test the code on the Test Server. These customers should be commended for assisting in the development process, but instead, their reports aren't even read.

It's a shame.

Sincerely.

down for 3 days, ha!

they need atleast 1 week to fix this mess if they would work on DEs but they dont so it takes a month for the most serious bugs to be gone and i dont think new bugs will stop popping up every patch.

More often than not it is management that forces bad code to production. They are usually driven by deadlines and schedules so heavily that they will say "I know it doesn't work but put it out anyway and we can fix it later". So go easy on the devs... it is the dev management that is pushing bad patches.

There is a saying for managers like this... "You want bad.... you get it bad"