Posted by combalt on 3/31/2018 8:46:00 PM (view original):
Posted by gencoimports on 3/31/2018 1:58:00 PM (view original):
Posted by FB_Trap on 3/31/2018 12:29:00 PM (view original):
Posted by matthewjohns on 3/31/2018 1:55:00 AM (view original):
If you guys could just fathom the enormity that seble has undertaken, you'd cut him some slack. It's a one man show as of right now. He's doing a great job.
With respect, matthewjohns, while I do acknowledge the size of the IT mountain seble had to climb having climbed one or two myself, and while I don't wholly lay the problems at his feet--unless he was the one making all the decisions as to how this was done--the fact is we pay for this service and have a right to expect competence from SportsHub. However, the number, scope and seriousness of the problems encountered with the migration, and the fact they all seemed to catch seble off guard, would seem to indicate that SportsHub didn't even do one dry run. In other words, they used us, the customers, as QA testers. And we got to pay them for the privilege. The sick twist is that if they didn't have enough resources (one guy for a mission critical project? Really?) and wanted to use us as testers, they could have set up a test server, done a dry run migration using a backup of the site and opened it to any of us who wanted to dive in and poke around for problems. I suspect many of us, myself included, would have been happy to do so. The result would have been not only a smoother transition of the live server but a quicker one, something that quite possibly could have avoided the wholesale shift in season schedules that will, taking the (ignored) feedback voiced by numerous players, cost SportsHub customers. So, with all of that said, I'll finish by saying that I am generally willing and happy to give amateurs some goodwill and a pass when they make amateurish mistakes. A for-profit company to which I am giving money? Not so much.
Well said. Usually when a IT move is made and there are major issues, you back out of it, Of course that wasn’t followed here,
Yeah I'd guess that is cause they had to be off the old servers by the end of the month.
gencoimports obviously doesnt work in the software world. Server may have come off warranty. Platform may have had unsustainable patches that Seble was left with. Maybe he had to do a ton of manual tasks that a migration would allow automation for.
In the end WHO GIVES A ****. It worked didn't it??? This was probably one of the better migrations I've seen. Deal with the bugs, let him know what comes up, and he'll gradually work through all the action items.