overwatch – Mana Obscura

If I had to pick a favourite panel from Blizzcon, Blizzard Engineering would be near the top. Hearing how the various programming teams overcome technical challenges to produce games with incredible polish is always interesting, particularly as their passion always comes through in their enthusiasm on-stage.

While there was only the one session this year, the Blizzard Engineering panel at Blizzcon 2018 still had a few interesting tidbits. Compared to last year’s deep tech examination, this year saw more of a focus on engineering culture, quality approach, and delivery methodology. There was a clear demonstration that it’s not just about problem-solving, but collaborating as part of a team that’s becoming increasingly important.

However, if I had to ask for one thing for 2019, it would be to repeat a request for more discussion around architecture. System componentisation came up a few times during the panel, but yet there was never an explanation of why it’s important or what value it provides. Likewise, many of the questions were from hopefuls looking for advice on getting a job at Blizzard, indicating a strong need for a separate careers fair at the event.

Before I get into a summary of the panel, I’d like to give a little attribution to those on-stage:

Somer Esat (Panel Chair) – Senior Engineering Manager, Overwatch
Rachelle Davis – Senior Software Engineer, New project. Previously an original member of the Hearthstone team, and has been with Blizzard for 7.5 years
Bruce Wilkie – Principal Software Engineer, Overwatch. Specialist in game engine and graphics rendering.
Diane Cochran – Lead Engineer, New project. Previously lead on Blizzard’s approach to Continuous Integration, lead on battle.net desktop app. Worked on authentication, public API, and has been with Blizzard for 8 years.
Collin Murray – Lead Software Engineer on WoW. Has written code for Diablo, Starcraft, Warcraft III, and every version of WoW. Been with Blizzard for 23 years.
Sarah Doebler – Technical Lead Battle.net. Started as a GM, has worked on Blizzard.com, the Armoury, and Content platform. Now leads tools team on battle.net, and has been with Blizzard for 14 years.

Continue reading “Blizzard Engineering – The Nuggets from Blizzcon 2018”

It’s not often when you hear engineers talk about the games they’ve been working on. It’s like a peek inside the machine, or under the hood. So it’s no surprise that I was pretty geeked out when I heard that two CodeCraft panels would be running at this year’s Blizzcon. As it turns out, the sessions were a trove of information on how Blizzard develops and operates its games.

I was surprised by just how much Overwatch has led the way in new techniques for the studio, being a testing ground for everything from having no downtime on patch days, to using a hybrid cloud infrastructure. Then there’s World of Warcraft, and what it’s like to manage a 10+ year-old codebase on a living game. Under that, it was surprising to discover just how much falls into Battle.net, and that’s without considering the areas covered by Service Support or Web & Mobile teams.

If I was going to ask for more from the presentations, it’d mainly be about the architecture. As a former software engineer turned enterprise architect, I’d love to discover if they have an enterprise domain model in place, or if Blizzard uses a methodology like TOGAF. Putting my personal asks aside, here’s some of the juicy nuggets from the two Q&A sessions held at Blizzcon 2017.

Continue reading “Blizzard Engineering: The Nuggets from Blizzcon”