| Redisplay Messages: Compact | Brief | All | Full Show Messages: All | Without Replies| Author: | aftepes  | | Posted: | Aug 20, 2014 17:05 | | Subject: | Re: BL Development Team: Test before rollout! | | Viewed: | 59 times | | Topic: | Suggestions | |
|
| In Suggestions, QCBricks writes:
| | True, but that is different than steering 90% of the threads into "Well BO does
it..." or whatever. I have never said that there should be no discussion. My
issue with the handful of people that clearly have an agenda.
Something like the currency issue was a real, easily understood issue. The whole
"the MOC shop team can just work on the main site" argument is just conjecture.
(as an example)
As I have said, it is not just the major issues, it is every single little issue
that gets turned into "OMG!!!11!!!1!1 BL is on the decline" from the same
handful of users. That is not the same thing as constructive discussion that
happened on some of the issues you mention.
Scott
|
I'd love to see this list of individuals who have the agenda and your opinion
on what their agenda consists of.
|
 |
| Author: | aftepes | | Posted: | Aug 20, 2014 17:02 | | Subject: | Re: BL Development Team: Test before rollout! | | Viewed: | 56 times | | Topic: | Suggestions | |
|
| In Suggestions, QCBricks writes:
| | You haven't done that by now?
What does the 100th message saying the same thing accomplish?
Scott
|
It says that my frustration is building, but I haven't reached the breaking
point that I actually act on a viable option. It says that you still haven't
addressed my concerns. It says a lot actually. It might also say that while I'm
looking elsewhere, I still want this to succeed.
|
|
| Author: | calebfishn | | Posted: | Aug 20, 2014 16:56 | | Subject: | Re: BL Development Team: Test before rollout! | | Viewed: | 38 times | | Topic: | Suggestions | |
|
| In Suggestions, QCBricks writes:
| | In Suggestions, TheBrickGuys writes:
| | In Suggestions, lovaquero writes:
| | Bricklink World Class Programming & Customer Serivce team -
Test before release. This concept is not hard. Perhaps in your eagerness to
pacify the crowd with pitchforks and torches you have forgotten it. Perhaps you
may just not know. Here is how you do it:
For EACH (individual) change to Bricklink:
-----------------------------------------
#1 - Scope your change to know its impact
#2 - Write your test plan to match the requirements for the change
#3 - Recognize that there are at least three (3) internet browsers to support:
Chrome, Firefox & Internet Explorer (IE)
#4 - Make sure that the test plan fails before any change is made
#5 - Implement the change, and only that change, in a development environment
#6 - Execute the test plan (in an isolated environement that matches the live
environment) for Chrome, Firefox and IE
#7 - Repeat steps 5-6 until the test plan passes for all three (3) browsers
#8* - Run the full test plan on the ENTIRE site to ensure everything still works
#9 - If anything fails, return to step #1 and repeat
#10 - Release the change to the live site.
(* Bricklink is written with ancient software that has so many dependencies,
querks, gotchas and 'hidden' features that it is impossible to know what
a change will do to seemingly unrelated features. That is why the software used
to run Bricklink is no longer used nor even supported, not even by the company
that originally created the software...)
Your new mantra must be: "test! Test! TEST! And then test it again!"
Any modern development team worth being paid - especially one that performs
web development - knows this.
Regards,
Rodney
Software Systems Engineer
Solution Infrastructure - Guidance & Machine Automation
John Deere Intelligent Solution Group
|
Thats a nice pitchfork and torch you carry.
Can you elaborate on what some of these horrible bad things are that BL has recently
done that now make it impossible for anyone to ever use BL again?
So many scream change CHANGE C H A N G E !! then.... oh wait
I dont like this change. I SAID I D O N T
L I K E T H I S C H A N G E ! !
Jim
|
Jim-
Logic is of no use. Bricklink is in a complete no-win situation at this point.
The 20 or so people that seem to live to instantly criticize them will do that
here in the forum no matter what Bricklink does. (or how well/poorly they do
it)
Fortunately for the complainers, they will have a whole new host of minor issues
to blow up over on Friday when the MOC shop opens.
Scott
|
i don't donsider it a minor issue that my buyers cannot view important information
about my store.
|
|
| Author: | legoman77 | | Posted: | Aug 20, 2014 16:50 | | Subject: | Re: BL Development Team: Test before rollout! | | Viewed: | 63 times | | Topic: | Suggestions | |
|
| In Suggestions, QCBricks writes:
| |
True, but that is different than steering 90% of the threads into "Well BO does
it..." or whatever.
Scott
|
John P
|
|
|
| Author: | QCBricks | | Posted: | Aug 20, 2014 16:40 | | Subject: | Re: BL Development Team: Test before rollout! | | Viewed: | 69 times | | Topic: | Suggestions | |
|
| In Suggestions, mnementh writes:
| | In Suggestions, QCBricks writes:
| | All true, but coming into thread after thread saying the same things over and
over accomplishes nothing.
|
How do you know that?
I know many features that BrickLink currently has that took YEARS or arguing
in the forums to get implemented.
Think Multiple Currencies.
Think Fixed exchange rates.
Heck, even inventories took a while to get implemented.
Perhaps we complain about things that don't work in the hopes that they will
be fixed.
Eventually.
Troy
|
True, but that is different than steering 90% of the threads into "Well BO does
it..." or whatever. I have never said that there should be no discussion. My
issue with the handful of people that clearly have an agenda.
Something like the currency issue was a real, easily understood issue. The whole
"the MOC shop team can just work on the main site" argument is just conjecture.
(as an example)
As I have said, it is not just the major issues, it is every single little issue
that gets turned into "OMG!!!11!!!1!1 BL is on the decline" from the same
handful of users. That is not the same thing as constructive discussion that
happened on some of the issues you mention.
Scott
|
|
Next Page: 5 More | 10 More | 25 More | 50 More | 100 More
|
|
USA, Maryland
Canada, Ontario
