Originally Posted by ssh
I'm sorry, and I know this will upset people, but no, we cannot go back.
I'm really wondering how "we cannot go back" from ssh aligns with Bob Barnes' reply to my thread about business continuity and disaster recovery plans if this small internet startup Huddler.com tanks, like so many others have.
Great post, Mark. I'm sure we all share the same concerns.
But you'll be happy to know that these issues were, indeed, discussed at great length, and they have been resolved to the satisfaction (delight is probably a better term!) of all parties.[/quote]
Bob says that contingency was planned for. Steve says "we can't go back".
IMHO as a 20+ year software engineering professional, this migration should have been done in a way that they could revert to the old platform within 24 hours. With no posts lost from either platform. There should have been, and should be right now, a daily export of all posts and membership data from the Huddler.com database (whatever it is) to a format that could be imported back into VBB. Obviously something like this had to have been created to go from VBB->Huddler in order for the 1-day migration we saw in the past week. I'm guessing that nobody thought to make it a requirement to develop it in a way that it could go in reverse. Whereas they should have done so as a baseline requirement for migration, and that reverse migration export should be happening every single day, just in case it is needed.
Unless "we cannot go back" is not a technical description but rather a business statement that really reads as "suck it up, we're not going back, we've bet our money and ownership on Huddler and hope to get a big payoff when MicroYahoGoogle buys EpicHuddler".
If that's the case, just be straight with us, folks. You owe it to your community of members and supporters who never signed up for a "Product Review Platform" when we invested hours (years?) of our free time and our supporter dollars (meager though they are) to make EpicSki.com the wonderful community it has been for years.
If that's not the case, and "we cannot go back" is truly a technical constraint, then in my not-so-humble professional opinion, this precipitous migration was horribly planned and not up to any professional software engineering standards. You ALWAY have a backout plan, and have it ready to implement both for the "crash and burn" scenario (not what happened, thankfully), and also for the "users/customers almost totally reject the changes for not meeting their needs" scenario - which is exactly what happened here.
For examples of where bad premature migrations were done but backed out, Northwest Airlines about 1.5 years ago (when they were still independent), rolled out a totally new "prettyfied" reservation booking engine site within their overall site. It was a disaster - many valid fares didn't come up, search options didn't work right, award searches didn't work. After about a week of feedback from loyal NWA customers/FFers, including a huge feedback thread on Flyertalk.com, NW reverted to the old booking site for about 3 months while they addressed the problems. New version fixed rolled out again, and though some people had problems with different look-and-feel, everyone got used to it because all the functionality people needed was added/fixed, along with new "cooler" features. Continental Airlines did something similar about 2 years ago with a failed rollout and a partial revert. Both companies' initial rollout decisions were flawed, but they had a way to revert and were willing to do so temporarily, rather than the "hang tough" attitude we're getting here.
Huddler might be a much better platform for where the Epic Owners want to take their investment. It might even be potentially a better platform for the vast majority of Bears, once they build in the missing functionality we had in VBB. But right now it does not meet the needs of the membership, and though I do wish everyone involved well, it is increasingly clear that this rollout was a major mistake.
Edited by MarkXS - Wed, 04 Feb 09 04:04:11 GMT
Edited by MarkXS - Wed, 04 Feb 09 04:08:42 GMT
Edited by MarkXS - Wed, 04 Feb 09 04:05:10 GMT