Technical Direction at Blizzard
Filter mode:
Topics
Media
asset system
data structure
database
game engine
language
library
memory
performance
platform layer
ui
(null topic)
🗩Speech🟉
Credits
?
?
W, K, P / S, J, N Jump to previous / next timestamp
t / T Toggle theatre / SUPERtheatre mode
V Revert filter to original state Y Select link (requires manual Ctrl-c)
X, ShiftSpace Toggle category and focus previous
v Invert topics / media as per focus
Keyboard Navigation
Global Keys
[, < / ], > Jump to previous / next episodeW, K, P / S, J, N Jump to previous / next timestamp
t / T Toggle theatre / SUPERtheatre mode
V Revert filter to original state Y Select link (requires manual Ctrl-c)
Menu toggling
q Quotes r References f Filter y Link c CreditsIn-Menu and Index Controls
a
w
s
s
d
h
j
k
l
←
↑
↓
↓
→
Esc Close menu / unfocus timestamp
Quotes and References Menus and Index
Enter Jump to timestampQuotes, References and Credits Menus
o Open URL (in new tab)Filter Menu
x, Space Toggle category and focus nextX, ShiftSpace Toggle category and focus previous
v Invert topics / media as per focus
Filter and Link Menus
z Toggle filter / linking modeCredits Menu
Enter Open URL (in new tab)⏫
Previous: 'Asset Systems and Scalability'
⏫
0:00: Introducing Marco Koegler
0:00: Introducing Marco Koegler
0:00: Introducing Marco Koegler
1:10: Give us some background
1:10: Give us some background
1:10: Give us some background
1:26: Studying computer science, participating in flipcode1 and joining the fledgling Crytek to work on Far Cry
1:26: Studying computer science, participating in flipcode1 and joining the fledgling Crytek to work on Far Cry
1:26: Studying computer science, participating in flipcode1 and joining the fledgling Crytek to work on Far Cry
4:41: At Crytek, what's the difference between Technical Director and Lead Programmer?
4:41: At Crytek, what's the difference between Technical Director and Lead Programmer?
4:41: At Crytek, what's the difference between Technical Director and Lead Programmer?
5:02: Technical Director and Lead Programmer combined role at Crytek
5:02: Technical Director and Lead Programmer combined role at Crytek
5:02: Technical Director and Lead Programmer combined role at Crytek
5:54: Applying to Blizzard as an Engine Programmer
5:54: Applying to Blizzard as an Engine Programmer
5:54: Applying to Blizzard as an Engine Programmer
7:56: How long have you been Technical Director at Blizzard?
7:56: How long have you been Technical Director at Blizzard?
7:56: How long have you been Technical Director at Blizzard?
8:00: Technical Director for almost four years
8:00: Technical Director for almost four years
8:00: Technical Director for almost four years
8:12: What is the team structure and hiring process at Blizzard?
8:12: What is the team structure and hiring process at Blizzard?
8:12: What is the team structure and hiring process at Blizzard?
8:57: Blizzard's structure, with sub-studios
8:57: Blizzard's structure, with sub-studios
8:57: Blizzard's structure, with sub-studios
11:15: World of Warcraft team structure
11:15: World of Warcraft team structure
11:15: World of Warcraft team structure
12:02: Engineering groups: 1) Gameplay
12:02: Engineering groups: 1) Gameplay
12:02: Engineering groups: 1) Gameplay
12:14: Does World of Warcraft require more than average gameplay programming?
12:14: Does World of Warcraft require more than average gameplay programming?
12:14: Does World of Warcraft require more than average gameplay programming?
12:26: World of Warcraft's original team size and "happy medium" development approach
12:26: World of Warcraft's original team size and "happy medium" development approach
12:26: World of Warcraft's original team size and "happy medium" development approach
14:18: Engineering groups: 2) Server, maintaining the live service
14:18: Engineering groups: 2) Server, maintaining the live service
14:18: Engineering groups: 2) Server, maintaining the live service
15:51: Engineering groups: 3) Database
15:51: Engineering groups: 3) Database
15:51: Engineering groups: 3) Database
16:36: Engineering groups: 4) Tools
16:36: Engineering groups: 4) Tools
16:36: Engineering groups: 4) Tools
16:52: Engineering groups: 5) Graphics engine and platform support
16:52: Engineering groups: 5) Graphics engine and platform support
16:52: Engineering groups: 5) Graphics engine and platform support
19:37: Engineering groups: 6) UI
19:37: Engineering groups: 6) UI
19:37: Engineering groups: 6) UI
20:01: This is a staggering number of teams
20:01: This is a staggering number of teams
20:01: This is a staggering number of teams
20:12: Engineering groups: 7) Systems, e.g. build systems, content delivery
20:12: Engineering groups: 7) Systems, e.g. build systems, content delivery
20:12: Engineering groups: 7) Systems, e.g. build systems, content delivery
21:01: Engineering groups: 8) Shared technology
21:01: Engineering groups: 8) Shared technology
21:01: Engineering groups: 8) Shared technology
22:14: Engineering groups: 9) Automation, e.g. performance measurement, stress testing
22:14: Engineering groups: 9) Automation, e.g. performance measurement, stress testing
22:14: Engineering groups: 9) Automation, e.g. performance measurement, stress testing
24:33: How big are these teams?
24:33: How big are these teams?
24:33: How big are these teams?
24:53: Total 65 engineers on World of Warcraft, and partner Engineering Manager Jonathan Moon Shaw
24:53: Total 65 engineers on World of Warcraft, and partner Engineering Manager Jonathan Moon Shaw
24:53: Total 65 engineers on World of Warcraft, and partner Engineering Manager Jonathan Moon Shaw
26:30: How do people come to Blizzard?
26:30: How do people come to Blizzard?
26:30: How do people come to Blizzard?
27:32: Blizzard's job application process2
27:32: Blizzard's job application process2
27:32: Blizzard's job application process2
32:44: Is the phone screen standardised?
32:44: Is the phone screen standardised?
32:44: Is the phone screen standardised?
33:18: The phone screen in Blizzard's application process
33:18: The phone screen in Blizzard's application process
33:18: The phone screen in Blizzard's application process
34:59: So the phone screen is intended to regularise applications?
34:59: So the phone screen is intended to regularise applications?
34:59: So the phone screen is intended to regularise applications?
35:27: How complex is the code test?
35:27: How complex is the code test?
35:27: How complex is the code test?
35:56: The code test is data structure analysis- / transformation-based
35:56: The code test is data structure analysis- / transformation-based
35:56: The code test is data structure analysis- / transformation-based
37:56: Blizzard's internship and University relations programs
37:56: Blizzard's internship and University relations programs
37:56: Blizzard's internship and University relations programs
39:38: What does the University relations program entail?
39:38: What does the University relations program entail?
39:38: What does the University relations program entail?
39:54: Blizzard's University relations program
39:54: Blizzard's University relations program
39:54: Blizzard's University relations program
40:38: Do you receive a similar number of internship and full position applications?
40:38: Do you receive a similar number of internship and full position applications?
40:38: Do you receive a similar number of internship and full position applications?
40:54: Three or four résumés come to the managers
40:54: Three or four résumés come to the managers
40:54: Three or four résumés come to the managers
41:34: Graduate applications, with distinctive and accessible hobby projects
41:34: Graduate applications, with distinctive and accessible hobby projects
41:34: Graduate applications, with distinctive and accessible hobby projects
44:37: Is there anything more on the hiring process?
44:37: Is there anything more on the hiring process?
44:37: Is there anything more on the hiring process?
45:23: Cover letter
45:23: Cover letter
45:23: Cover letter
46:27: What does a new hire do on day one?
46:27: What does a new hire do on day one?
46:27: What does a new hire do on day one?
47:24: Day one at Blizzard: Onboarding, scavenger hunt, meeting the team
47:24: Day one at Blizzard: Onboarding, scavenger hunt, meeting the team
47:24: Day one at Blizzard: Onboarding, scavenger hunt, meeting the team
49:17: Day two at Blizzard: Arrive to desktop set up with code downloaded and compiled, starting on a small bug with the lead programmer
49:17: Day two at Blizzard: Arrive to desktop set up with code downloaded and compiled, starting on a small bug with the lead programmer
49:17: Day two at Blizzard: Arrive to desktop set up with code downloaded and compiled, starting on a small bug with the lead programmer
52:49: First check-in and code review
52:49: First check-in and code review
52:49: First check-in and code review
53:35: How does the code review work?
53:35: How does the code review work?
53:35: How does the code review work?
53:53: Code review at Blizzard
53:53: Code review at Blizzard
53:53: Code review at Blizzard
55:37: After this first code review, are they now in the general assignment pool?
55:37: After this first code review, are they now in the general assignment pool?
55:37: After this first code review, are they now in the general assignment pool?
55:48: Gradual widening of expertise and exposure to complex systems
55:48: Gradual widening of expertise and exposure to complex systems
55:48: Gradual widening of expertise and exposure to complex systems
56:48: What makes a good team member, and what do you tend to wish new programmers come in already knowing?
56:48: What makes a good team member, and what do you tend to wish new programmers come in already knowing?
56:48: What makes a good team member, and what do you tend to wish new programmers come in already knowing?
58:31: Good habits: 1) Asking a question
58:31: Good habits: 1) Asking a question
58:31: Good habits: 1) Asking a question
59:31: Good habits: 2) Internalising that we're all in this together
59:31: Good habits: 2) Internalising that we're all in this together
59:31: Good habits: 2) Internalising that we're all in this together
1:00:41: Good habits: 3) Being proactive
1:00:41: Good habits: 3) Being proactive
1:00:41: Good habits: 3) Being proactive
1:00:56: Good habits: 4) Bridging the gap to art and design (communication)
1:00:56: Good habits: 4) Bridging the gap to art and design (communication)
1:00:56: Good habits: 4) Bridging the gap to art and design (communication)
1:02:33: Good habits: 5) Having played the game and knowing the lingo
1:02:33: Good habits: 5) Having played the game and knowing the lingo
1:02:33: Good habits: 5) Having played the game and knowing the lingo
1:05:10: Good habits: 6) Being great engineers, able to break complex tasks down and make progress
1:05:10: Good habits: 6) Being great engineers, able to break complex tasks down and make progress
1:05:10: Good habits: 6) Being great engineers, able to break complex tasks down and make progress
1:06:53: What do you tend to wish new programmers were better prepared to do?
1:06:53: What do you tend to wish new programmers were better prepared to do?
1:06:53: What do you tend to wish new programmers were better prepared to do?
1:07:26: Preparedness: 1) Project experience and understanding organised team work
1:07:26: Preparedness: 1) Project experience and understanding organised team work
1:07:26: Preparedness: 1) Project experience and understanding organised team work
1:11:15: Preparedness: 2) Lifetime, memory and resource management
1:11:15: Preparedness: 2) Lifetime, memory and resource management
1:11:15: Preparedness: 2) Lifetime, memory and resource management
1:11:55: That seemed to fall into two categories: lower-level programming knowledge, and higher-level decision making
1:11:55: That seemed to fall into two categories: lower-level programming knowledge, and higher-level decision making
1:11:55: That seemed to fall into two categories: lower-level programming knowledge, and higher-level decision making
1:12:56: Write code, and only solve as much of the problem as you need
1:12:56: Write code, and only solve as much of the problem as you need
1:12:56: Write code, and only solve as much of the problem as you need
1:13:18: Did I miss anything?
1:13:18: Did I miss anything?
1:13:18: Did I miss anything?
1:13:40: Not every engineering position is the same
1:13:40: Not every engineering position is the same
1:13:40: Not every engineering position is the same
1:14:52: Talk a little about 16-year lifecycles
1:14:52: Talk a little about 16-year lifecycles
1:14:52: Talk a little about 16-year lifecycles
1:15:17: Dealing with old assumptions and 32-bit vs 64-bit architectures
1:15:17: Dealing with old assumptions and 32-bit vs 64-bit architectures
1:15:17: Dealing with old assumptions and 32-bit vs 64-bit architectures
1:20:44: Technical debt in the content creation pipeline
1:20:44: Technical debt in the content creation pipeline
1:20:44: Technical debt in the content creation pipeline
1:24:05: Talk a little about hot-fixing
1:24:05: Talk a little about hot-fixing
1:24:05: Talk a little about hot-fixing
1:24:14: Hot-fixing, with centralised development database
1:24:14: Hot-fixing, with centralised development database
1:24:14: Hot-fixing, with centralised development database
1:30:26: Thank you, Marco
1:30:26: Thank you, Marco
1:30:26: Thank you, Marco
⏬
Next: 'Large-scale Systems Architecture'
⏬