These are just my opinions but I think there is ample evidence for them, and yes it impacts all system developers exactly as you would expect. It’s quite easy to show with proper testing how even minor changes can have drastic effects on forward results. And at the same time even proper testing cannot guarantee that even a minor change didn’t negatively effect forward results. Inadvertent bugs are another very real risk from changes. The only way to truly validate is to run a system live, and that takes time. It’s hardly responsible to do forward testing live while your customer’s money is at risk without their informed consent somehow. At the very least, IMO, customers need to be made aware when a system changes and that forward results might have been impacted. As I mentioned I also think a good approach is to release a “Version 2” and let customers switch as they see fit.
Honestly, I’m pretty certain I’ve got a handle on how to tweak, improve, do whatever I think is best for my system. But, that’s only my opinion; because I won’t disclose everything about my system in an attempt to convince you that … “I’m good.”
I proudly notify my subscribers when I make improvements. They are grown and realize that they are free to unsubscribe for 6 months according to your protocols; or not. That’s for each individual to decide–not me. They’ll be welcomed back in 6 months (probably at a higher subscription price, however).
So, once again, we’ll just have to wait and see how my approach works for my system; and how your approach works for your system.
Best of luck.
Post must be at least 20 characters.
You too Dave.
.____________________.
“Luck is what happens when preparation meets opportunity.”
― Seneca
