billywoods wrote:daal wrote:Why are we talking about yours?
I'm reporting a (serious) bug. It's not relevant or helpful for you to come along and respond with how few problems
you're having. It doesn't make any sense for people to be telling me that I should be really grateful for all the fun games of go I can play
in theory.
Before I answer your question directly, I'll tell you a little bit about my background so that you can understand the reason for my question. In real life, I'm a project manager in the IT industry. For a project to be successful, it's essential to understand what assumptions are being made and what the various expectations are. People have a variety of expertise and varying degrees of technical and business jargon and specialised vocabularies. Therefore, having everyone share the same understanding of what's required is essential.
That's why I asked you about your IT industry background. If you told me that you're a high school student taking your first programming class, then I'd use different terms and concepts than if you told me you have 20 years as a developer in commercial environments.
Now let's get back to your paragraph above. You state as a matter of fact that the lag is caused by a KGS bug. I don't agree with this yet. We haven't yet eliminated your computer, your cables, your firewall, your wireless router (if you have one), your local network infrastructure and so on and so on. There are lots of things which can cause lag. To state as fact that the only cause is KGS code is simply premature.
Because you see this lag being caused by a bug, you are apparently frustrated that Bill hasn't fixed it. However, if the cause is not the KGS code, then the cause of the problem is outside of KGS' control. Diagnosing and fixing connectivity faults can be quite complex in some circumstances. (In a previous job, we spent considerable time and hundreds of thousands of dollars fixing a communications problem for a bank.) Simply assigning the cause to KGS without actual proof of it originating there isn't going to solve the problem.
billywoods wrote:(As for BigDoug: I am not convinced in the slightest that he wasn't just being patronising, like several of the other respondents to my posts. I could be wrong. In any case, I've already made my IT expertise clear in this thread and elsewhere.)
Before you assign negative intentionns to me, why don't you consider why I'd intentionally patronise you. You raised a question about KGS and I tried to answer your question. If I have a question about go and someone asks me my rank in order to find out how best to explain it to me, I don't take that as a personal affront. Personally, I'd expect someone to speak with a 6D differently than a 15K. That's not to say that the 15k is in any way inferior. It's just a matter of know what terms and concepts are best to use when speaking with the person. (Note that I'm not implying that I'm a 6d and you're a 15k or vice versa -- this is a example only.)
I've worked in the IT industry for many years. I would be personally affronted if a fellow professional made fun of someone because he or she is a student or works in another industry. I don't know what you received your university degree in, but the odds are good that you're much more knowledgeable in that field than I am. If I politely ask you a question in good faith, I would expect you to try to answer it and not make fun of me for not being as knowledgeable as you.
In addition, the odds are also quite good that someone else in this thread is more knowledgeable about these technical issues than me. And if that person tried in good faith to help, I would not assume that he or she is patronising. I'd assume that the person is simply trying to help.