Even with your argument of it being an expected time of completion, that’s still a failure.
I know real people are working on this. This failure is NOT their fault. It’s the failure of the project manager who either naively or willfully allowed their project to run behind schedule and left everything to the last minute.
Well, that’s just silly. I’m not even going to play a blood elf.
I never said that. I said that is something happens. I’m all for holding people accountable for their responsibilities (which again, I don’t blame the people trying to fix this issue for. I blame the people who managed the project and didn’t anticipate that this might have been an issue and have a plan in place for it).
Well, Space goats are at least sort of cool, so there’s that.
The project manager is a real person too. Unless Blizzard has developed sentient AI. In either case, you can’t really be all that upset at them. Projects are pushed back all the time at every company, ever. I’m not sure it’s as simple as flipping a switch to make this all work as intended. It’s a Frankenstein freakshow. They have to get it right, and by their own admission, they’ve never tried this before. Cut them some slack. They’re working to get this up and running so it doesn’t take a dump on everyone all at once when we log on.
You can plan for everything and still be surprised. Not a hard concept to understand.
Not out of the way at all. You posted here whining about the state of things. In fact, it was low hanging fruit.
And then people have to justify why these things happen to their superiors and develop processes to prevent such a thing from happening in the future. PMs also should be having meetings where situations exactly like this one are talked about and possible solutions raised before any project gets off the ground. Accountability is important, and arguably more important is listening to the people who are going to be doing the work.
I can almost guarantee that there was one or more person in the planning meeting that specifically mentioned this exact scenario and they were dismissed or met with “everything will be fine”.
Except they had time to do at least a limited test conversion of the process ahead of time. Blizzard entirely set the timeframe.
Again, I’m not saying that the people who are actually doing the implementation aren’t worthy of praise; lord knows I’ve been stuck in the exact situation of implementing software where something doesn’t work right, and every time after those situations in the companies that I’ve worked for, the question that is always asked is “how can we make sure this never happens again”. I’m just concerned based on the fact that so many people are saying “this is just how blizzard be yo” that after implementation meetings aren’t happening at all, or if they are, no one is looking at the lessons learned before the next implementation takes place.
I agree, the outrage is a bit much… But I have to point out it’s 2021. The discussion about having to split servers and it being difficult is a joke unless they are really bad at IT.
I am willing to bet the servers are virtual if not containerized. Creating the 2 copies and controlling access via the client access systems (since there are 2 classic clients now) should have been in place and tested before today complete with the locks and blocks to require the “copy service” for access to both for the same character. Each copy would have everything as of shutdown, it just a matter of locking and allowing access to one or both.
Most likely they ran into an issue with the tbc patch causing a glitch or unforseen bug… or something in the infrastructure crashed when the servers were brought down showing a problem that they didn’t know about in the hypervisors or storage. Those things do happen. Even the best IT departments run into “oh crap” moments no matter how well planned and how good prep is.
I will admit that it does seem to happen to blizz a lot more then I would expect.
*** One issue they have is that backing out is not really an option. They talk about x happening and people expect it. If they run into something that was unexpected, they have to work it out and fix the issue on the fly. They are going to avoid backing out of something this big 99.99999999 percent of the time because people would go nuts if they come out and say “We found something that will take a while to fix so we are going to postpone the changes for x weeks”.
stop simping for this garbage company my god the deflection is so unbelievable
How much do you pay for your sub each month? Until you unsub, you have no ground to stand on. Cry harder.
30 hours a week is part time. Most of us “productive” members of society work 40 hours a week at MINIMUM. Personally I work 49-53 hours a week so yeah I guess my time is a little more important than that of someone who works less hours than I did while in high school.
and so is blind corporate shilling
Want donuts now…
Let’s be honest, this is a better release than BC the first go. lol
Same as above. Here you are, on the forums, whining about a game you pay to play. You’re a corporate shill as much as the rest of us. Stand for your principles. Unsub and go find a nice quiet room to moan about your problems in.
I actually did mate, back in November and I upgraded an old expansion I had and they added 30 days of game time. Trust me mate, I’m here to watch Rome burn.
Blizzard’s standards is now the US govt’s. Sounds about right.
completely relative, you could shovel **** for 49 hours a week and he could perform neurosurgery for “less hours than you did in high school”
on top of that, no **** you think your own time is worth more than someone else’s, because you’re selfish AND entitled, hilarious.
Oh, so you have absolutely no stake in this at all. Cool. Your opinion matters even less now.
ya cry harder, typical response from you degenerates so far up this company’s A$$
bootlicker