Everybody is right! From what I've read from other treg testers, the consensus seems to be that once they started using the TB and talked to Mark, even those who were critical of the delays felt differently. Oh, they may still have liked to see it ship - well, at least those treg testers who came later and thus received much better devices than the first group did - but they could see the reports on Slack of testers who had issues, or experienced them for themselves, and better understood just how complicated this is.
But, since everyone is right, it is an unfortunate fact that most have not had that experience and no matter how often they hear these observations from treg testers, it isn't the same thing as seeing for themselves. So, logically, to them it just seems like too long for these issues to still exist - or that WT is trying too be too picky. From what they can actually see, their comments make sense.
There really is no ideal solution. If WT is right and it needs to be better, it would be foolish to ship. And they really can't ship just to those who say they won't complain if there are problems because as soon as they would start doing that, everyone would suddenly claim they won't complain either - yet many will. Even if they don't complain to WT for support help, they'll be posting about their problems elsewhere.
So, no ideal solution. But that's why I keep pushing for updates that gives us something to measure progress with.
Let's look at some of the WT comments in just this thread. Keep in mind that there is nothing wrong with these comments - but they don't actually measure progress:
There is a measurement there (95%), but it was months ago that there was a referenced to only 5% having issues so it doesn't actually show a measurable improvement (it could also be just a generic phrase all people use, not meaning specifically 95% but just to establish that the overwhelming majority work fine).
Which is certainly good, but does not actually measure progress to the customers.
It is good to know it is "mostly the firmware subtleties", though that is pretty vague. And doesn't tell us what is not "mostly". I can think (strictly theoretically) of other things that are involved in manufacturing a product since my family comes from a manufacturing background. Things like ramp up production which can reveal manufacturing issues that don't show up at lower rate of production. But, in the case of the TB, we really have no idea what things are issues that are not firmware.
Anyway, a lot of the updates contain comments like those I quoted. All well and good, but without something more, customers are being told there is progress but not info that actually measures progress. As I said in an earlier post, don't need to know about each "whack-a-mole" issues that may still be popping up. Just info on progress in general categories would be good.
And many people still think you are looking for perfection, no matter how many times you have said you aren't. Maybe it would help if there was information like, "About 5% of testers experience bt/connection problems on average once a day. We need to get that down to 2% averaging maybe once a week."
BTW, all these examples I give in my various posts aren't intended to mean I think you should do all of them. They are just examples and I feel that certainly some of them could be covered.
Or, to put it another way - quoting someone who was very upset with me on a totally different subject - "Here's some free advice and it's worth every penny"!!!
I don't think they realized what they were saying!