Reply to thread

Message

<blockquote data-quote="Herschel" data-source="post: 5380338" data-attributes="member: 78357">Unrealistic expectations from armchair computer &quot;experts&quot;.&nbsp;Seriously. How many people complaining about the initial bugs at role out have actually done any QA testing? I know I have on different programs for different companies and I can say that none of them were without a lot of bugs upon role out.&nbsp;Why? Because QA can't find everything and QA can only simulate, not actually run with all users. I'm not a regular QA person, I was brought in on projects because I'm an end user with some skills. My normal position is not to build, code and load test and I was brought in after roll out because of issues that weren't found. &nbsp;I'll give an example, in a major database there were a number of bugs. I was assigned to help QA test prior to an update. I crashed it with a fatal error in my first half hour that was undiscovered because I was trying to do something they hadn't thought of. &nbsp;Yay for me, right? Well, I hammered around in it myself, running it through edge cases I could think of, and QA handled it. But when the update went live? Boom! An error surfaced around what I had tested that I had approached from multiple angles and it still wasn't found.&nbsp;&nbsp; &nbsp;Add in that people were pre-building disappointment before it was ever released and the general lack of patience in our society it's not surprising people are upset, but that doesn't make all the expectation reasonable. It appears updates are happening fast and furious as things develop. &nbsp;But hey, pitchforks and torches are more fun, right? &nbsp;Also, all the complaints about Silverlight I find rather funny. Just because someone read on the internet that brand new *platform B* is all the rage doesn't make it a good business decision to go that route. The number of people who feel the need or run the &quot;latest &amp; greatest&quot; is relatively few. From what I see and ask around, Silverlight seems to have made a lot of sense. &nbsp;Don't get me wrong, missing features and such are a pain, but what should have been expected in a brand new roll out vs. the expectations some had? Some times a little patience is all it takes. Jumping to conclusions within 24 hours of a rollout (or even before, as some have) is ridiculous. &nbsp;Heck , I didn't experience any of the issues last night that people were complaining about&nbsp; even earlier in the day. &nbsp;Sometimes a little information/background is worse than none.</blockquote>

[QUOTE="Herschel, post: 5380338, member: 78357"] Unrealistic expectations from armchair computer "experts". Seriously. How many people complaining about the initial bugs at role out have actually done any QA testing? I know I have on different programs for different companies and I can say that none of them were without a lot of bugs upon role out. Why? Because QA can't find everything and QA can only simulate, not actually run with all users. I'm not a regular QA person, I was brought in on projects because I'm an end user with some skills. My normal position is not to build, code and load test and I was brought in after roll out because of issues that weren't found. I'll give an example, in a major database there were a number of bugs. I was assigned to help QA test prior to an update. I crashed it with a fatal error in my first half hour that was undiscovered because I was trying to do something they hadn't thought of. Yay for me, right? Well, I hammered around in it myself, running it through edge cases I could think of, and QA handled it. But when the update went live? Boom! An error surfaced around what I had tested that I had approached from multiple angles and it still wasn't found. Add in that people were pre-building disappointment before it was ever released and the general lack of patience in our society it's not surprising people are upset, but that doesn't make all the expectation reasonable. It appears updates are happening fast and furious as things develop. But hey, pitchforks and torches are more fun, right? Also, all the complaints about Silverlight I find rather funny. Just because someone read on the internet that brand new *platform B* is all the rage doesn't make it a good business decision to go that route. The number of people who feel the need or run the "latest & greatest" is relatively few. From what I see and ask around, Silverlight seems to have made a lot of sense. Don't get me wrong, missing features and such are a pain, but what should have been expected in a brand new roll out vs. the expectations some had? Some times a little patience is all it takes. Jumping to conclusions within 24 hours of a rollout (or even before, as some have) is ridiculous. Heck , I didn't experience any of the issues last night that people were complaining about even earlier in the day. Sometimes a little information/background is worse than none. [/QUOTE]

Verification