User blog comment:Dracko40/The Angry Illithid: Delays and miscommunication/@comment-3360527-20110708045532

Being a person that works in computer maintenance and network maintenance, I am going to use my personal first hand experience with electronics to explain this to you. When something breaks and/or goes wrong, there is probably a good 60-80% chance that I will not be capable of giving a deadline for when it will be fixed because fixing broken shit is not the same as creating a product. Computers can be tempermental and moody. They can sometimes 'choose' to not do exactly what they should be doing according to their programming and code. The REASON why they havn't given a deadline is because they don't KNOW when it will be fixed. Especially when its a rare CRITICAL error that they probably havn't come across yet before.

As far as you're complaint about not communicating the problem, you are just dead wrong on that account because they ARE communicating the issues as they can. Would you prefere it if they came out and said there was going to be server downtime because they're 'predicting a bug to pop up'? They're not psychic and therefore can only tell you after they know and not before they know.

Also, just because they know what the problem is DOES NOT mean they know what the issue is that is causing the problem. Symptoms and the problem itself are NOT THE SAME THING. Yes the can be in the same area, but not always. The hardest part of troubleshooting can sometimes be finding the issue that causes the problem.