View of the bug - customer

Back to "view of the bug" topic. I will try to fix previews post. This time I will try to look from different perspectives of more people who are affected by bugs of system. I will focus on my experience, so in couple month or years everything can change and this info will be not relevant or I will have more knowledge. But today I hope it is.
Starting from the bottom. Customer.
Now I will try to split customers in two groups. I will call them beta tester and working customers.
First group are actual customers who decided to work with product which is still in development stage. Sometimes this decision is for training or acceptance purposes, in other cases this is way to get product cheaper or get knowledge from that area where product is focused.
When customer knows that product is still in development for him to find a bug is not huge problem. Just to get fast response and hot fix is main requirement. This beta tester customer provides good info and feed back and gets updates and fixes faster. So this case finding bug is not such big deal for customer or company.
Funny part is working customers – they are people who wants to get the best and well working product. This time then bug appears – things can get crazy. Situation – customer decides to get rid off the old product and get new "my" product. "My" product have more features and other stuff which is not supported by previous product. Everything seems working fine, but after some time customer finds issue which for any reasons blocks customer from work or at least requires additional work to maintain working with this bug. From customer issue comes to support, later it is approved, fixed and tested, new release comes and only, only after some time fix will be introduced to customer.
Imagine how person or company should feel if they had to work with issue for month, maybe two or even a year. And how much customer is furious if he finds out that fix will come after two months or longer.
For this type of customers new bug can be unpleasant experience (softly saying).
This post doesn't seem very wrong for me. Two types of customer, it can be more, like something in between, customer which is same company, or something from specific area there bugs just can't occur. I didn't go to much left or right, tried to scratch surface, I hope I did what I wanted. Part 1 of unknown. 

Your friendly neighborhood Tester

Sitting together is good, sitting together is bad

Days like today I came up to the bugs which I can't reproduce and my colleague can't work because of this issue. We have one difference - I am sitting in same room with developer and he is sitting in other side of world. Does this situation makes me better or worse tester?
According ISTQB book independent tester or testing team provides better results (I think there was even a diagram of independence), because they aren't affected by developer or other same environment factors. I'm trying to think it through, and I see few pluses and minuses in this situation, regardless if I am independent or same environment player.
Pluses of sitting near developer would be that You get knowledge from first hands, and You can setup environments more "correctly" and easily, came to issue with more knowing about its roots than just from bug description. But pluses really soon becomes minuses. If You have developers knowledge about issue so in a way You see issue like developer who was fixing it. And like everybody he(or she, it doesn't matter, just for this situation leave it as he, next time maybe it will be she, I work with males and females developers) is protecting his work and can't truly see an issues clearly. And this confidence and don't believing affects me and I start to get careless. Loose my focus and can't work as that person who is miles away and is the closest to client point of view. Other minus I can think is eating lunch, joking or just chatting with same people, with whom You will need to work later and check their work, can make You irrational to decisions about founded issue.
To sit far away from developer, literally or theoretically, gives advantages of independent thinking. You aren't affected by developers sweet words, minds or his knowledge. You do what You must – testing. Project description mostly is available, bugs have reproduce steps. Seems everything can be fine and doing Your work goes to best result. But here comes disadvantages – lack of first hand knowledge, understanding, which sometimes goes to 1+1=3 is true and without knowing that You are working with things You don't know. This can lead to reopening same bug again and again until someone will provide information, or mentality differences will not make You see an issue, or maybe without small chat with developer You wouldn't be able to think test case which leads to issue. Or even more – sometimes testing projects that doesn't have much info, so without developer help – several bugs are founded and fixes, system kinda works, but without internal company or team knowledge,  final product isn't what is needed to be or it is, but lack of knowledge not all major issues was founded.

Now You are thinking – "this is what he is writing can be fixed with couple documents and calls". OK, yes it can, but knowing people helps, talking and knowing more than it is written helps too. But overall everything depends on Your (I am talking about myself mostly, so "my") attitude and view to work. Any body can be independent(now coming to theoretical part) or You are sitting in same room or miles away. But more knowledge You have about shit and fruits You are fertilizing, better they will grow.
Yes, independent tester or team is great, but situation not always allows that, independent must be mentality and view. So sitting close or sitting far can be just mental state, and by sitting in same room You can provide similar or greater results. 

Your friendly neighborhood Tester.