Blizzard was never a privately held company or not in the sense that founders had real autonomy. I believe Michael Morhaime had a lot to do with why Blizzard could do what it did. I remember reading in interviews that he defended the soon(tm) mindset and steered the owners away from chasing quarterly reports. I also believe that Chris Metzen was a key figure in upholding a geeky and fun culture. I was genuinely impressed by Blizzard in my youth and dreamed of working there one day.
But something happened after the success of WoW the company grew quickly and with that came some bad people and after the merger, Bobby Kotick could exert his influence.
Blizzard stopped being a geeky place for geeks and culture eroded slowly.
I also believe that the original core Blizzard people were struggling with leaving the company in the hands of the next generation. They wanted to believe that the people they had in the company would carry the torch and embody the same ideals. It didn't happen.
The saddest day was when Metzen announced his departure. It was felt by many as a shock. He was a beacon of hope and light but I also think the was struggling with some personal family matters. He now felt the work was no longer in his best interest and left. A lot of Blizzard veterans followed suit. I don't think a single one of the original people still work there, with the exception of Samwise Didier. Blizzard still has a very strong art department.
I believe Michael Morhaime did what he could but ultimately realized that he didn't have the autonomy to fix it. The problem had grown to big. Maybe they were naive? I mean, these people struck gold and built one of worlds most renown gaming brands and the worlds most successful MMO to date.
On the flip side. All the key people have moved on to found new gaming ventures and I believe this time they've had the capital to fund it themselves. Hoping they stay independent and build great experiences for us to enjoy.
Metzen Knew about the toxic “bro-culture” while he was in one of the management positions directly above some of what turned out to be the worst sexual offenders, and did nothing about it, for which he apologised on his own Twitter post scandal.
Michael Morhaime similarly was the head of Blizzard doing the worst of the sexual misconduct and people don’t things like “cube crawls”.
I’ve worked in big enterprise, I know how easy it is to turn the blind eye to things (maybe not drunk employees litterally crawling around to harass women) but still, but I fear that the toxic culture may be as old as Blizard west itself, and that it likely only grew into the sexual misconduct that it did following the growth of World of Warcraft and the huge influx of new hires (including a lot of in-office women which had been rare up till then).
If they knew and did nothing that's bad but somehow I don't believe these people didn't care or didn't try to tell these people to behave.
In a company with thousand's of employees how can you expect a few people to be responsible for everybody, that's just absurd.
You come to a point where you've said and done all you can and nobody is listing. At that point you will make yourself very unhappy staying. This is why I think these people, who are genuine geeks, ultimate just left Blizzard and hoped the people they left in charge could bring it into the next generation.
Company is doing well but the brand has take quite the blow.
If I had an employee that I repeated told not to get drunk and crawl around hitting on coworkers. I would fire that person if they didn’t stop. To be perfectly blunt, I would have fired them right away, but I’m Danish, we can do such things with little repercussions since it’s so blatantly insane that they would have no ground to defend their actions.
Morhaime and the leadership definitely had autonomy. Blizzard was the goose that laid the gold egg. Also multiple former employees have stated that there's no way Morhaime didn't know what was going on. So I think you've got it backwards.
Both Mike and Metzen state in the own response that they didn't realize how bad it was and they only respond this way because this lawsuit got huge press.
Why is it so hard to believe that when you're running a company from above you have virtually zero knowledge of what's going on in the trenches.
And the people around you act as layers to insulate you to some extent. The only way you change that is by building trust between your peers and even if you go out to dinner together the topic of discrimination and harassment probably won't come up. Most people won't just say out loud what they think needs improvement unless you ask them.
You can fault them for not being more proactive but they most probably believed that the people they did trust to be on top of these things actually did what they said they would do.
It's the hardest thing to build and maintain a delicate culture. It takes just a few rotten eggs to ruin everything.
I guess we agree on one thing then - that's the exact reason that I don't believe all the press about Kotick fostering a culture of harrassment. He can't possibly be across everything that's happening at a dozen or more studios with over 9,000 employees.
> But something happened after the success of WoW the company grew quickly and with that came some bad people and after the merger, Bobby Kotick could exert his influence.
I don't think this was the case, and that rather WoW's success forced the company to become more professional but the sexual harassment culture was so ingrained that the company couldn't shake it off. The name thrown around the most due to the lawsuit was Alex Afrasiabi, who was hired in early 2004 to work on WoW (which released November 23, 2004). You can also take a look at WoW's credits [1] and see the mention of "sexy HR girls" or their internal tenth anniversary video [2] from 2001 that covers why they hired their first female employee.
A couple of weeks back the youtube algorithm decided to show me the youtube channel of one of the Warcraft 3 level designers who worked for Blizzard from 1998 to 2003, and in one of his videos, made 4 years ago mind you, he's pretty clear on what the culture was like there [3], with the choice quote "if I wanted to bring a sexual harassment lawsuit against Blizzard ... I could have easily done that."
The guy also said that Rob Pardo (lead designer of Starcraft, Warcraft III, and WoW, and now founder of Bonfire Studios since his ejection from Blizzard in 2014) was particularly toxic. And it seems he's not the only one with the same sentiment [4]. The other Rob from that tweet I'm guessing was Robert Bridenbecker [5], who was with the company since 1995. These were people that had to have been working closely with Morhaime due to the nature of their positions, so keeping them around for so long despite the outstanding HR complaints doesn't bode well.
Is it worth following and supporting the new gaming ventures if this is the culture those veterans fostered and had grown accustomed to?
I've seen it. I have also seen a lot of disgruntled employees and it's not obvious to me that I should take anyone's word over senior management.
With the kind of success that WoW had it goes to your head. Some people get corrupted by it. It can bring the worst out of some people. That probably happened.
Lots of people want to work in the video game industry, so they'll put up with low pay, long hours, and apparently sexual harassment for a really long time.
Unfortunately, the situation is similar throughout most of the entertainment and sports industry. Employees want to work in the field so they put up with abuse and unprofessional behavior that wouldn't be tolerated in more staid industries.
Working a at FAANG is not as attractive to most when you don’t know about the issues in the video games industry. There is a reason why FAANG companies pay well and video games companies don’t have to.
I met zero people who told me they dreamed about working in a FAANG since childhood.
There is no mention in the article about these people being engineers. These people were fired "to address allegations of sexual harassment and other misconduct". These are the bad guys. And finally, there isn't that much overlap between "perf tuning in AAA game engines and improving cloud workloads".
Both your sentences are true. So, what do we conclude from them though? It doesn’t change the core fact that the cost of skilled labor is lower for games companies than it is for FAANG, right?
It's also possible that in a creative industry like that you can't be as controlling when it comes to employee behavior. The people coming up with crazy new ideas are probably more eccentric than average. It might not be as easy to walk the line of separating the good eccentric behavior from the bad. An incident here, an incident there can pile up over the years. My impression is that it's not a very uncommon problem in the entertainment industry.
CPython compiles Python source code to bytecode, but it never compiles the bytecode to machine code. Instead it interprets the bytecode, reading one instruction at a time, and basically calling a giant switch statement that handles every possible opcode.
A JIT would compile the bytecode to machine code then run it directly (at least for frequently executed code paths). There is no "switch" anymore. Each bytecode instruction has already been replaced by the corresponding machine code.
> Is there any reason why official python doesn't have any JIT option?
Desires to keep the implementation simple and approachable (relatively), as well as avoid issues of performance cliffs and such.
Also the C API has historically been extremely broad and provided large access to what amount to implementation details, making this keep working properly with a jit is difficult (at least for anything but a simplistic macro-ish JIT).
PyPy is not fully compatible with CPython. You won't have the same behaviour and CPython C API is not guaranteed to be fully compatible. So, I'm not sure that having a JIT that is fully compatible is easy.
Most terms in language implementation are fuzzy. But just in time compilation most often refers to switching from interpreting bytecode to (generating machine code and running that) generated machine code in specific spots after having analyzed the currently running bytecode for a while.
"Classical" (again, every term is fuzzy) JIT compilers either do this machine code compilation after seeing a good candidate _entire function_ or a good candidate _section of code within a function_. Good candidates are often areas of code that are executed a large number of times and with consistent internals (e.g. iterating from 0 to 10000 with variables inside that have provably fixed types).
But there are infinite variations of JIT compilation.
In any case, CPython doesn't do that switching from bytecode to generated machine code. Pypy does do that. As does V8 and the JVM and so on.
I'm interested in chatbots for learning foreign languages. In that scenario I really don't care how dumb the conversation is, just that it's grammatically correct.
I would have said "Try the support chatbot on some big service provider web site that uses your target language", but that would presume that chatbot programmers (or programmers in general) can write grammatically correct prose, so... Maybe not.
" A significant problem with the current implementation of PSDoom is that monsters are much more likely to attack each other than expected. This causes many windows to mysteriously disappear as the program runs"
