Out of Play Area, a game dev podcast by John R. Diaz Ep 27: James Kane (QA Manager & Designer @ Raccoon Logic) Published Feb 28, 2022 ยท 78 min Episode page: https://outofplayarea.com/podcast/ep-27/ Transcript (machine-made, lightly edited; may contain errors): [0:02] John: On episode 27 Out of Play Area, the game developers podcast. I sit down with a good buddy in arms from my days at WB Games Montreal, James Kane. He's a game designer and QA manager over at Raccoon Logic based out of Montreal. We talk about his journey into the industry where he worked up through QA, let alone even finding that that was even a valid career path. We talk about how he made the change and jumped into WB Games Montreal out where we got to work together. We talk about how he transitioned to typhoon studios, where he latched on to being part of a scrappy indie team of pros, where he got to wear multiple hats. And he got to put his game design studies to use on unreal, where he worked on Journey to the Savage Planet. [0:45] John: We talked about what it was like getting acquired by Google stadia and then reforming up as raccoon logic. Please welcome all the way across the border from the Sub-Zero climate in Montreal, Quebec, Canada, James Kane. Let's start the show. [1:04] Catherine: Bienvenido Bienvenue Welcome to the Out of Play Area Podcast a show by video game devs for game devs, where the guests open up one-on-one about their journey, their experiences, their views, and their ideas. No ads, no bullshit. Join us as we venture far out of the play area with your host seasoned game designer, John Diaz [1:28] John: do you drink in friend? [1:29] James K: So I got myself some four roses, single barrel, Kentucky, straight bourbon whiskey. [1:35] John: That seems like it's a special, thing to you. [1:37] James K: I was in Tennessee visiting my mom cause she lives out there and her husband just likes himself some good whiskeys. And he was like, Hey, have you. ever had this? Cause it's from Kentucky, like right next door. And I was like, no. And like every bottle is like signed for it came from everything. It's it feels a bit more personal and man, it just goes down so smooth. There's no burn. It's just a really good whiskey. [1:59] John: when I [1:59] James K: Yeah. [1:59] John: four roses. I don't know why I, I picture that building in Montreal and the canal, [2:04] James K: Yeah. I know. and weirdly you can't get this alcohol and Montreal. if I ever wanted again, I have to go to Ottawa to get it. think maybe it's because there's no French on the bottle. I have no idea. [2:12] John: That'll do it. You gotta localize. Otherwise Quebec ain't having it. [2:15] James K: but it's, it's a really good whiskey. It's just super smooth. It's like a nice, a chill nights whiskey. [2:19] John: You take away the ice, [2:20] James K: Oh yeah. I've got quite a bit of, [2:22] John: especially in this. [2:23] James K: yeah, especially cause we're in a heat wave right now. So I mean all the ice helps. [2:26] John: Yeah, buddy. I Chis saute. It feels like it has been forever since we had like a happy hour Fridays up in the Warner brothers tower over in, what's the name of that? Is it Barry? You came, yeah. That's the name of the Metro stop? [2:40] James K: you cam, and then up in the WB place that was Central perk. named after the the friends cafe. [2:47] John: That's special, man. I got a bunch of family that they love friends we're always having the discussion. Like, is it friends or is it how I met your mother? And I'm definitely team how I met your mother. [2:55] James K: Oh man. That's a tough one for me, honestly. Like they're both good in their own ways for me. Right. [3:01] John: a thing, right? Like they came at a different generation. [3:04] James K: I think there's more episodes I would go back and just, I, I just love watching from how I met your mother. Cause like you can watch one-offs and they're just so well done. And I feel like France has a few of those, but friends, most of them are more like up episodes, right? Like, oh, it takes like two or three episodes for, the big, impactful thing to happen. So it's harder to just drop someone into a random friends episode where they don't know context was how I met your mother. It seems pretty simple. [3:27] John: Each episode can stand alone. As long as you know, the characters [3:30] James K: Yeah. Yeah. [3:32] John: I get you it's been too long, but at the same time, it feels like no time has passed [3:37] James K: Yeah. It's been a hot minute. [3:38] John: so much has changed. Where are you at today? [3:41] James K: Oh, today? Well recently announced I'm at a new studio in Montreal called raccoon logic. it's a lot of like ex typhoon guys who started up studio. After our fun rounded, Google. But yeah, so I'm going to be a junior designer the head of QA. [3:58] John: Okay. So a hybrid role, but it makes sense if it's a small team, you wear multiple hats. [4:03] James K: Yeah. Typhoon was the same thing, but it was the opposite. It was, I was head of QA and a junior designer. So I did like a little bit of design work and my main focus was to lead their QA. Cause they were so tiny. They just needed someone who had pretty good knowledge. And now it's like the role reverse. It's like, Hey, they need someone to help a bit with QA to get it started, but I can finally do the design I wanted to start doing. [4:24] John: Okay. So more design than QA, whereas on typhoon, it was more QA. [4:29] James K: Yeah. I think at typhoon it was probably like maybe 75%. And now it's going to be more 75% design, but it really depends, right? Like if they get to a point where it's a huge crunch and they need a lot of help QA style, I will put design on the hold because it's more, I'm just there to help at the beginning. Right. So I'm there whatever capacity in enemy. And they got some pretty good rockstars in that team. So I'm you know, my design skills were a little low for my QA skills are pretty damn high. [4:53] John: I love how you always approach it. You always willing to learn and to be fair designers, once the game is already set, we turn into QA. Right? [5:02] James K: Yup. [5:03] John: at the point in the project where I imagine, right, a company hasn't even opened yet, you're going to need design. There's not going to be much QA. And then as the life groves, [5:11] James K: QAs interesting at the beginning of the project though, because you just want to make sure that you can showcase your bill to the team without a break. And that's all it's going to be. I feel like early, a lot of people silo their work and then just like throw it in the build, like on like a Thursday afternoon, because they want to show it in like, you know, the Friday show and tell or whatever. [5:27] John: Yeah. [5:27] James K: And I find like, yeah, when you're farther in production, don't do as big silos. And like now it's going to be like, all the designers can be working on their own maps, doing their own thing and they might not be submitting to the branch. So I gotta, you know, make sure that it doesn't break. [5:39] John: standup those processes and like checkpoints. Right. [5:43] James K: Yeah. It's more, I just make sure they're submitting more frequent than they normally would just so I can make sure the health stays good. So that's going to be my, my role as QA there. Just make sure that builds up busted and make sure it's working so everyone could assess what's going on and you know, get the ball rolling as fast as possible. [5:58] John: I want to ask you what it feels like now that you're building content. How would you empathize with people that are like holding on, not wanting to show anything don't want to check anything in until it's perfect. You know what I'm saying? But then also fighting your alter ego of like check it in rapid iteration. You know, don't hoard anything the sooner it's in the sooner we can identify any conflicts. [6:18] James K: I don't hoard anything in my design again. Maybe it's a junior thing, but I'm fast. [6:23] John: yeah. [6:24] James K: I prefer to get it in quick and then get people's feedback as fast as possible. Then take like a week to think I did a great, and it not be as good as I thought it was and then have to redo at anyways. Right. but it's interesting because I have that QA background, I'm really trying to check my stuff as much as I can. So, like, say I build a quest, a simple quest to put it in the level. I gotta make sure the rest of the levels still flows properly and make sure my question break anything. And then once I finished triggering, I can keep triggering other quiz. [6:50] John: yeah. [6:50] James K: Right. like, not, everyone's going to do that because you make sure your thing works and then if it works, you're good. Right. But been the difference with like me becoming a designer from QA is I feel like I QA my work a lot and it's not like I'm even thinking about it. I'm just doing it without thinking. [7:05] John: It's second nature to you, [7:06] James K: Yeah. And it hasn't slowed me down at all. if anything, like, I love pushing my workout as fast as I can. I'm still giving it the best quality I can. Right. but I try putting in a fast, because I really want to get people's eyes on it because I've seen too many times where someone takes two weeks and I'm like, Hey man, that just doesn't work. [7:22] John: Yeah, absolutely so much can change over that time. By the time you submit this merge conflicts, love it, bro. that takes veterans years to learn, right? So the fact that you already put it into practice, but you're a veteran yourself. You've been in the gang for awhile. [7:37] James K: Yeah. Just a different field. Right. [7:39] John: Hell. Yeah. You've seen enough wrong to know how to it, right. [7:43] James K: Yeah. You just see the things you're like, Hey man, this is just going to cause some weird stuff down the line. Let's just fix this now. Or it's also what I found really interesting coming from the QA side. So at typhoon for a good example, cause I did design their QA their game for like a year and you know, you know, the game inside and out and I can speed run that game pretty fast. So then it's like, if you're making something, I know if it's gonna the level at all, like, you'd be like, oh, it's a new mechanical. Yeah. But it doesn't feel good. Right. Or it's Ooh, that feels really good because it flows with this and that. And like it doesn't hinder my playing. [8:13] James K: Right. Which is, which is interesting because it's like, you know, most people just either design something on their own and like, Hey, it's cool. Cause it's, you know, a fun thing, but they don't have the whole scope of the game that they're thinking about. [8:22] John: Remind me the name of the game. [8:24] James K: Oh, a typhoon who was journey to Savage planet. [8:26] John: That's right. How fast could you get through that guy? [8:29] James K: I'm no speed runner. I think I, I get it in like under an hour, [8:33] John: Damn. [8:33] James K: okay. So there's two ways to beat that game. [8:35] John: I know it's on game pass right now. I've been meaning to get into it. [8:38] James K: You can either blast off the planet or beat the bosses to wind conditions. One takes a little longer than the other. I think the fastest one I can do just to get the credit screen and, you know, I, when I think is under an hour and then the full game. I think it takes about if we do multiplayer cause it's co-op we can do it in about like an hour and 20 hour and 30, but like, that's just, you have to know where every single thing is, divvy up the work and just blitz. [9:02] John: For what you do for someone on the outside being like, Hey, what does a QA director handle? What does a junior designer handle? How would you break that down? [9:11] James K: I'll start with the junior designer, cause I've been doing it so short, but that side was doing small things. So it was like implementing small question to the game placing collectibles resources and a lot of tuning, I think for typhoon, I did like all of the creature, health tuning player tuning for damage and health, you know, things that are simple and don't require me to break the game. And then I left the heavy lifting of like building all the systems and everything to the other designers. And on the QA side, That was managing a team of, we were only two people internally, but then externally we had at most, I think, 15 and at least maybe six. [9:43] James K: So it was making sure internally we were you know, smoking the builds making sure that if a programmer had something big, they were going to be checking in. We had to create you know, make our own build with that specific change. Make sure everything worked perfectly you know working with the devs, just to make sure that all their features worked internally before we sent it out to the QA teams to then them do their huge test passes that we'd be monitoring and we'd make for them. So we would give them you know, Can you collect all the things in the game argument scanning. So is everything scannable? Does it work? is it beatable? Can you get all the upgrades? [10:13] James K: You know, we'd give them their, their big test plan to do. And then they just churn through that test plan as fast as possible, give us our results and then we'd see what happens. So it was just managing them and then managing my one tester in generally. [10:24] John: do you go about laying out a test plan out of curiosity? [10:27] James K: I mean, you could do it a thousand different ways. Yeah. I know. So an example on a Batman game, right? You can make a combat test plan, which is huge. Cause it's, basically every single thing the Batman can do beat every ability against every single enemy in the game. Right. So that just looks like a giant matrix of. Fun. across that it's every upgrade and then can everything be, canceled if you get hit? So if you have a five chain combo, what happens if four, three to get hit? Right? So those are like your combat test plans. Then you have like AI test plans where you can make sure AI don't break. I've done that working with you and they're fun. [11:03] James K: So you give us the tools that we need to monitor them. And we, you know, there seems to be like a lot of soak tests involved where we'll leave the game overnight, perched up. Like Batman's a great example. Cause you can like perch above the enemies and then we just watch them and make sure they don't break. And that if we come back in the morning, they're still functional. And if you try to engage with them, they work fine. Right. [11:20] John: that's a good [11:20] James K: then there's destructive test plans where we'll just say break everything into zone, hit every wall you're checking for, you know, collision issues. test plan. It could be anything you can think of. You can turn into a test plan. My test plan for typhoon is really what was my smoke test. And it was just every ability in the game scan and kill every creature then do a request. And then I just kind of took that, gave it to them and said, Hey, this is the base version of it. You know, do all that and kinda just do a bit of halo testing around everything, just to make sure that we didn't miss anything. [11:46] John: I don't think I've ever heard the term halo test. [11:49] James K: as you got ad hoc testing and halo testing can just go do stuff with just it's off the books. So basically let's say I give you a combat test plan. There might be stuff I didn't think about, or there could be stuff that is super situational that may never happen. Like in Batman, you can use a gadget off of a car to kill an enemy. That's stuff. because it's procedural have some of the world loads, so maybe that stuff would never happen. So I'm like, Hey, you're the combat expert, testers go nuts and break combat, you know, your test plan is your, your guideline. But some people don't like doing a checklist. Some people are way better. If I just say, Hey, you do combat, go break it. [12:25] John: Yeah, totally. [12:26] James K: So we give them like the ad hoc or the, the halo testing that they do For the day. people really don't like checklists. I personally love them, but some people, some people thrive without it so much better because they get super creative. [12:38] John: Yeah. Yeah. And it allows them to be creative in a job where you wouldn't normally think that's a thing you get to unleash. [12:44] James K: Oh, a hundred percent. [12:45] John: How do you empower it better? How do you spot it? You know, to be like, okay, He, she, or they are on my team and okay. There are list person versus, okay. They're more of like a free reign person. [12:56] James K: So I WB I was only a senior there, but I had some control over some people and we did a lot of test plans on Batman. you would see how people would act throughout the day. Is it someone who is going through their checklist and like two hours or a day? Right. Is it someone who likes it? Cause some people will love it and they'll, they'll say it like, like, Hey, I just finished. Can I have more, like, I'm enjoying this. Some people are like, Hey yeah, it's done. And like, that person. doesn't want to be doing that, [13:19] John: Dead in the face. Yeah. [13:21] James K: but then you have to see like, because there's a lot of, you know, the publisher wants bugs, right. And the whole point of this checklist is to find the bugs. if I give you the ability to go do your ad hoc, you bugging, are you finding useful things or are you finding more useful things when you're on the checklist? Right? Cause art's a big one. Art will have like Hey bug, everything in like Yeah. Right. And then you go there and it will be whatever severity we say. Okay. And it could be as low as grass clipping into a wall to, oh, we only want big objects that are higher than your knee. Right. And you know, some people thrive with that, but other people just want to run around and not be stuck in a zone and feel like they're not really moving. [13:58] John: Okay. Interesting. That makes total sense. [14:00] James K: if you're good QA leaders talk to your testers and make sure they, they want to be open with you too, because you don't want it to be a crappy job that, you know, you don't like doing. Cause there's, there's always going to be a part of it. That will be fun for someone, [14:12] John: yeah. It's always slotting in your, people, in the right spot. [14:15] James K: yeah. Cause some people love looking for those weird art bugs and they have an eye for it too, because they know. [14:22] John: Mm. [14:23] James K: Right. And that helps too. And some people don't and then you put it on it and you see the huge difference in what they find and how their, their week goes. [14:31] John: Yeah. You know, it's interesting. I've always felt that you were a very approachable person, open to communicate, give feedback, take feedback, always wanting to learn. And so I find you were a lead or director of my boss, it was kind of an open door, right? Like I should feel no hesitation to come over and talk to you about like, oh, I want to do something else, or I want more of this. curious, how have you felt your team and that culture? [14:55] James K: Oh, I love it. Yeah. I love it. Like I've had bad leads and I only say they're bad leads because they don't want criticism on what you give them. They don't want you to come talk to them. They just want you to do your job. And like, I get it. You want the job done? Me. Tell me everything, man. if you don't like what I gave you, just tell me you don't like it and we'll figure it out. know, it has to get done some way shape or form, but if we can find a better way to get it done, that makes you enjoy your job. I'm all yours. [15:22] John: Yeah, man. [15:23] James K: And, this is weird thing where outsource QA they feel like they don't have a voice a lot of the time, because they're just in this giant machine of you give them a build from a random company and they write bugs, right? and when we were on journey, no one was talking to us really. Cause I feel like they had this, they thought that everything they said had to go through their lead and their lead would have to be very specific on how they would word things to me. Because for some reason they think I'd be insulted. I guess they might've worked with people in the past. And we saw that, like they just weren't talking much. And we were like, Hey, please tell us everything. [15:53] James K: I don't need it to come from your boss. I know if that's weird for you guys. Just talk amongst yourselves, but like. Anyone could say anything. You guys can DME specifically, you don't even need to talk in the chat. If you feel like your question is stupid. For some reason, like there's no dumb questions, but if you feel like it is poke me directly, everything matters. And that team became so talkative and their bugs started changing dramatically because we started saying like, Hey, if you think our systems are bad, bug them, but don't just say it's bad. Give me your reason and think as a designer on how you would make the system better we may not fix it, but we might, and some other suggestions came through and we fixed like certain quests that felt weird for them. [16:29] James K: And but normally you can't do that as an outsourcer that no one lets you do that. [16:33] John: Yeah, I've seen those dynamics. I've been in those dynamics, right. Even when you are a support studio to a primary studio, right? Like an example is a rock steady to a WB working on Arkham night rockstar San Diego supporting rockstar north as they're working on a GTA, right? Like it's funny initially upfront, even though we're all kind of the same team, the fact that we're separated by a physical building creates these invisible little barriers and we all operate like super like, okay, I'm going to talk to you through my manager. And my manager is going to relate the thing. [17:04] James K: I got worse for you though. Okay. When we were at WB, we were a floor apart and we had those problems. [17:10] John: Yes. I [17:11] James K: Yeah, [17:12] John: and it was, it was amazing to me because I would journey between the floors, right. Be it for snacks, for meetings. I'm coming back from basketball and checking up on some of the people and you could totally feel it. It was like a force field. It was [17:26] James K: yeah, [17:27] John: your badge not open the same doors that my badge does? [17:30] James K: It doesn't. Yeah, us. We were not allowed to go on your floor. And I think if I'm correct, there was this thing where we were technically two different companies. [17:38] John: Oh [17:40] James K: you guys were WB games, Montreal. And we were like, Whidbey. It was like WB interactive entertainment or something. [17:47] John: yeah. [17:48] James K: And it was weird enough that that's what it was. So like, they separated us in that way, but it was so annoying. Cause we were testing your game. You guys were downstairs and I couldn't talk to you and we weren't even allowed to like message you on the internal messaging systems or anything. [18:02] John: Which is crazy to me because I come from the same mentality that you have. I'm [18:06] James K: Yeah, [18:06] John: playing my content. Tell me what you feel, bro. And it's up to me as a designer to interpret it work back and forth with you to see like, okay, what do you really mean? What do you feel? Where are you seeing it? How does it work? Right. You're like any feedback is good feedback. [18:21] James K: of course. [18:21] John: it's up to, me, as the creator to give you the vocabulary, to let me know exactly what I need to know kind of thing. [18:30] James K: you know, typically dev QA comes in in these situations where you guys will be, you know, super close to the dev QA, cause they're on the floor with you. They could be embedded on your design team and then it's their job then relay all that info to the outsourcers or the publishers QA [18:46] John: Okay. [18:46] James K: building or another building. it's just, it's awkward because that like singular dev QA has a job to do, they also have to manage a bunch of information, take requests. Like it's just, you get bogged down. It's a weird system. [18:59] John: So you mentioned dev QA. again, this was, this was a whole different world for me, right? Like I just thought QA was QA, there's apparently a single tree with many different branches on that sucker. [19:10] James K: you want? a few little breakdowns. [19:11] John: Yeah. Please [19:12] James K: I don't know everything. I'll tell you what I know. So you got your outsourcers, they're your big, your big powerhouses of QA. They can take huge contracts and lots of contracts. [19:21] John: Okay. They usually juggling a bunch of different projects. [19:24] James K: yeah. And it's usually where you start as QA. started that like 13 years ago at a place that doesn't exist anymore in Montreal. [19:32] John: What was the name? [19:33] James K: It was a VMC, but they got eaten up by the big keywords and they're like keywords. It's like a powerhouse of QA right now. [19:38] John: Okay. [19:39] James K: Not saying this is bad thing. Just that's what they are. So keywords is a huge outsourcer. Outsourcers can also have sub-departments of localization. So you have your low QA. Sometimes those are in-house as well. Like they could bloke can really be in. does your studio want to have a full-time Loke? Probably not. Does your publisher sometimes because they have the money for it and maybe they're, they're doing a lot of games, so it makes sense, but usually they're, your outsourcers, then you get your compatibility testers, which are just for PC usually. I've done that too. It's basically, you're building computers all day and you're testing hardware you'd usually do a really big pass and you're, you're trying to find the min specs. [20:15] John: Yeah, [20:16] James K: So you're trying to find out what this game can run on what the lowest settings could possibly be. But it's so hard because it's testing different amounts of Ram different motherboards for processors, all the graphics cards, internal graphics cards, It's a lot so compatibilities, if your game works on PC, be happy. Those people exist because it's a lot of testing. [20:34] John: As you talking about this, it makes me think of this amazing platform that is stadia and all the cloud gaming platforms. Right. That X-Factor is now kind of completely taken out, right? Like, [20:46] James K: Yeah, there was no compatibility testing on there at all. It turns into being more Like, a Microsoft or a Sony or Nintendo at that point. Right. [20:52] John: there's one skew [20:54] James K: Yeah. It's, it's the one build and that's all you need because you're streaming it. Whereas I mean, Sony and Microsoft are a little bit different now because they have, you know, now it's like, Hey, does it work on PS4 and five? And the pros, like, there's a little bit of testing, but it's normally not that bad because all they're really doing is giving you more Ram usually. So it's just, if it works on the base spec at work on the best on the high-end spec but PC is just a whole beast. So yeah, I, I actually, I liked that about stadia. It was interesting. Cause I really love the idea. as a dev making something on PC, you don't have to worry about it not working on someone's computer. [21:27] John: Hm. [21:28] James K: Right. That was cool. [21:29] John: Even in this work from home remote setup, man, like [21:32] James K: yeah. [21:32] John: to a bunch of deaf friends and they all test off of stadia. Like all the reviews are done on stadia. [21:38] James K: Yeah. I mean, you just know you're going to get the same performance as the other person. Right. So it's, it's interesting. it's not the best it's got its hiccups. But liked that for like a testing standpoint. It was really cool. Plus I don't need any special hardware. I can test it on my cell phone. Like it just worked so easily for testing. It was very fun to test on that for a year. [21:56] John: What you were testing on your cell phone? [21:58] James K: Yeah, man. [21:59] John: What do you do? Like a, Xbox controller, Bluetooth to your cell phone [22:03] James K: you could, but it has touch control. And there are not great for every game and they were janky at best for ours, but it worked. [22:10] John: That's bro. [22:12] James K: I thought it was so cool that I'd be like, cause it was like, Hey, can you make sure this build boots? I'm like, yeah, it's Saturday. like, I'm eating dinner. Sure. I'll just quickly press the button on my phone. It takes a second. Like, it's no big deal. Hey, look at work. Here you go. Thumbs up. [22:25] John: yeah. Can you imagine where we are today? Like I never thought we would ever get in this position of like developing from home, developing at our leisure super flexible hours. Right? Like being able to do our job [22:35] James K: yeah. [22:36] John: the clock, you know, as needed, you know, being [22:38] James K: And [22:39] John: kind of fit life in [22:40] James K: I remember early days of QA, I think it was like when the PS two was still pretty big and it was almost PS three time. [22:46] John: what's. This is like early two thousands. [22:48] James K: Yeah. And it was more waiting for disks to show up. So it's like, [22:52] John: for people to burn them and [22:54] James K: well, sometimes cause if it was a normal build, sure. The build master would get a disc and they would burn a disc and give it to us. But if it was like a gold master candidate, we would have to wait for the studio to FedEx them to our building because we couldn't burn those in house. They had to come from a special whatever. And I was like, man, that was crazy, [23:13] John: the difference between the gold master and the ones you burn in house? [23:17] James K: man. I don't know some weird Sony on that [23:20] John: Okay. they're burned by console heads. [23:22] James K: Yeah. Cause it's more like it's a legit copy of the game. Just not, you know, fully real. [23:26] John: But it's like the certified sone or certified X-Box with the little seal of approval. [23:32] James K: Yeah. I like that went away pretty fast. Cause even PS three, we had some downloads too, that we were able to do, like, cause we can download builds, but that was crazy. Cause I remember sitting in the office. like 10:00 AM and the guys like build should be here and I'm like, come on, man. He'd be here for hours. And then it a noon. And they're like, okay, we have to let you go because there's no work. I'm like, all right man. [23:49] John: Dan. So that's just burning money, right? Like the hours are ticking away [23:53] James K: Yeah. And all that's gone. So like that was horrible. It's so much nicer now. and then the stadia, just my mind exploded thinking back about how ridiculous that was. And now it's like, Hey, just go to the website and press play. It's like, [24:05] John: I love that. That's the thing that got me. I was at Amazon testing out Luna and that was the, main thing that kinda hit me in the face. It was like, I pressed the game and I'm loaded in. Yes. I mean, that's what sold me [24:18] James K: it was nuts. I know. [24:19] John: and the resume. [24:20] James K: Oh, yes. yeah. yeah, yeah. The, the state, the state, the same thing where you could just go back and press play and you're back to where you were SI and stadia was cool with that because I would start on my cell phone, make sure it worked. And then I could just go on the PC click and I'm back in game. [24:34] John: That's the best shit ever. [24:36] James K: That was nuts. [24:37] John: Going back to the branches of the QA tree. [24:40] James K: so we got your publisher QAs, [24:42] John: Oh, so these are these like first parties, Sony, Microsoft, Nintendo [24:46] James K: yes and no. Cause it's also like WB now rockstar will have their own. It's more, your in-house queue. but not dev QA. So it's more that weird structure we had at WB? where, they own the QA themselves. So it's a little bit nicer of a job cause it feels more permanent because that's also the fear of outsourcing is a lack of jobs and a non permanency. It's a big one. Whereas publisher is more of like, you know, when you feel a bit more secure in your job, but it's still, you're not dev QA yet. Right. And then sub part of that is the certification QA. So that's your, your Microsoft, your Sony and your Nintendo is, will be where you send your builds and you have specific QA who test them to give you your, your certification results to see if your game passes and is able to go live. [25:26] John: Gotcha. [25:27] James K: So you have a specific team for that. you have your dev QA. So your dev QA are your, embedded team QA. So usually there'll be, you know, a dev QA for the audio team and for the programmers, if it depends on how big your team is, right. And usually you can. [25:42] John: Per feature. [25:43] James K: Yeah. bigger your team, the more dev QA you want, because you really want them to be testing everything you do and make sure that It's as clean as possible because you have so many hands in that pie. You gotta make sure it doesn't break. And that's my favorite part is the dev QA, but it's also one of the harder ones to get into because there's not as many jobs [26:01] John: Yeah. It's my favorite man. I mean, it's [26:03] James K: I know. [26:04] John: the homeys, right? Like you guys are in the trenches right there alongside us, hearing the pain, helping us conquer through that. Right. And, and troubleshoot, [26:13] James K: Yeah. [26:14] John: a big proponent in our reviews and all of our meetings. Right? Like we kind of look to you to make sure that the build is loaded. It's it is where it needs to be be able to call out whenever we see something. Right. Like you guys kind of save our asses a lot of times, but oh yeah. We've seen this. This is known blah, blah, blah. Right. [26:31] James K: Yeah. I'll give you a little, little story for dev QA. Cause like I haven't been there for here for that long. I think my first time was at WB on a game that doesn't exist. Metallica. [26:39] John: Oh my God, my heart [26:40] James K: I know. [26:41] John: strings. [26:41] James K: that was my, that was my first dev QA job. I did like an internal one where I was at a studio and I helped them out, but they didn't treat us like dev QA. They treated us like QA who were literally sitting next to them. It was very bizarre, but this was my first time really doing deputy work. And I remember chatting to someone on the team who, I won't say names. I don't want to call anybody out, but they don't like QA had a bad taste for QA and we were chatting because there was only two of us on dev QA up there. I'm like, we were like, Hey, we don't want to be hated. So like, what's up? [27:09] John: Was it you and Christian [27:10] James K: Yeah, it was me and Christian [27:11] John: or shout out, shout out, to that main. [27:13] James K: the first, two dev QA up there. And yeah, they were like, QA, you guys just write all those stupid bugs about like grass clipping and walls and stuff. Like, you know, you flutter databases and give us these dumb bugs. We don't want, when all we want is, the big issues. And then I was like, man, we don't want to write those either. [27:28] John: Yeah, [27:28] James K: The only reason, the only reason those bugs exist is because your producer, your manager told my boss that you want like 30 bucks a day per QA. [27:37] John: there's a quota. [27:38] James K: Yeah. man, it's hard to find 30 crashes per tester a day. And like, for example, when we were on Batman, there was like over a hundred of us in-house then there was another team of over a hundred, right. So let's say, let's say 200 testers a day. They want like 20, 30 bucks each. [27:54] John: even with a game as big as Arcam was depending on the stage of production, right? Yeah. That is. [28:00] James K: it was buggy. Sure. But like it's hard. [28:03] John: Especially that PC one. [28:05] James K: the PC to be fair. Wasn't that bad? that came down to compatibility? [28:09] John: yeah. It was like the end video cards or whatnot. [28:11] James K: well, we looked at a lot of those crashes and they were like, there was no graphics card in that system. We're like, oh, that's probably why you crashed. [28:17] John: I could see that I can see that game, the hype, the hype level of that game, and people kind of downloading it they can get their hands on [28:24] James K: Oh yeah. yeah. You're like, whatever my, my, my system can run it. I got two gigs of Ram. But yeah, so we were basically like, look, you tell these giant groups of testers, they need these bugs. And the threat is, Hey, if you don't, you're fired. That's really all there is to we'll find someone that will get us bucks a day. So what am I going to do? I'm going to go, and I'm going to find my 20, 30 bucks. And it's going to be some crappy art, right? Like I don't have time to spend three hours looking into a crash, which I'd love to. But if I do, I potentially lose my job. Like that's a terrifying. [28:53] John: Absolutely. [28:54] James K: Like quotas are horrible. So when, when we explain that and we explain like, Hey, like we're, we're here to help you guys, whoever you guys want. if, what you want is for us to do an art pass for you, tell us the parameters of what you want And we'll bug it. If you want an audio pass or an AI pass, we'll do it. Just tell us the minimum bug you want. Cause if you don't say anything, we're just going to treat it like you want everything and bug everything. We'll get the big ones out of the way, but then, we're going to go granular and go small. But if you tell us, like in Batman, it was don't bug anything below the knee, anything clips below the knee, we don't care. [29:24] James K: Cause it's too small. [29:25] John: yeah. [29:26] James K: And it's like, cool. Tell us that. Like, if you don't tell us that we're just going to start. And like, we don't want to get like 4,000 invalid bugs in a day. It looks really bad. Right. And I feel like a lot of devs don't know this their producers and their managers know this. But the devs don't. So the devs are the ones that get swarmed with all these bugs and they just get this weird perception of QA and they just like running, writing crappy bugs all day. [29:46] John: That's why I bring you on to the show. Hey, well, a, I bring onto the show to drink with you, but [29:50] James K: Yeah. [29:51] John: thing is I bring you on the show to set the record straight man, and let people know who may not know that these are your marching orders as they come down. Right? And very often they are this made up figure. That seems to make sense on some spreadsheet of like, Hey, I have these many bodies. And if I asked them for this many bugs, odds are 10% of those are going to be super important. And you know, we're fixing kind of thing. [30:15] James K: Yeah. or it comes from a, another weird point where It's a dev plays a game one day and is like, Hey, this area is real buggy. Why aren't QA doing. [30:23] John: That [30:24] James K: And then they're like, Hey, the producer found nine bugs. Everyone who plays should be able to find nine bugs. And that's how a weird quote it gets imposed. [30:32] John: Yeah. That makes sense. Producers are often kind of like in there trying to earn their paycheck. [30:36] James K: Yeah. But then what the producers don't get is like that build will never see dev QA because the dev QA are going to bug at first. And like, it's just this, it sucks, man. [30:44] John: How would you fix this dilemma that plagues QA which in the form of quotas or the miscommunications that developers feel right? Like I've, always appreciated you guys. I appreciate QA everything you do and. When you guys come over in your inquisitive nature to learn, right? Like to what I see in front of me today, It's turned you into this super powered designer, right. That, checks his work before it goes in. And I just see an awesome evolution in front of me. So, [31:14] James K: I think it's a hard one to fix. Cause there's a lot of like, problems You need some good leads in the QA side, right? You don't need people who just want numbers and cause there's a lot of those. Cause there's a lot of people who got hired as a lead who have never done QA. Maybe they got some sort of degree for something that, whatever management degree they took somewhere. [31:33] John: what's a management degree. [31:34] James K: Yeah man. Well, you can do like a management course these days. It's like a weekend course and you get a, like a little degree you've you are a manager. I know at WB you need to do that if you want to be a manager. [31:45] John: Oh shit. [31:46] James K: Yeah. Crazy world. But I mean, I just feel like, or some people get promoted really fast for reasons, [31:51] John: Yeah, [31:52] James K: but you just don't want people who only want numbers. [31:55] John: for sure. [31:56] James K: And then those people just have to have real talks with the devs and the devs have to be open with it too. Right. Cause then, then you're talking to the producer on the dev side. Right. And that person has to be not again, just about the numbers and that's the big problem, [32:08] John: Don't just be about the numbers. Be about the quality. [32:11] James K: yeah. But I get it. Like if, if you see that it's been a week and there are zero bugs come in from your QA team, this is probably a problem. Right. And that's another thing, like bad thing, as I told you, outsource QA, it's like, people are worried about losing the job. It's also pretty low paying. [32:24] John: Oh shit. Yeah. So super volatile, high turnover. [32:28] James K: Yeah. But, people also just want to get out of it. no one wants to stay QA because the pay is bad. And that's a big problem because if you're like, Hey, going to be QA. So I can be a designer because there's a path there. And a lot of people do that path, but that shouldn't be your reason for Like it shouldn't be like, Hey, I want to be a designer so I can live and make money. It's like, no, man, QA should be good enough to be able to pay you to do your job. you want good QA because if you don't, what's going to happen is the people who become good QA leave [32:52] John: I definitely agree with that, man. Like wish it was a path that was nurtured and fostered and had a long road to grow fried to go through the whole ladder of like senior principal director ways to be better at the craft, right? Because an experienced QA person is worth, five juniors, if not more, you know what I'm saying? [33:13] James K: but they don't see it that way usually. Right. They're like, well, we'll just get five juniors. [33:16] John: Yeah, exactly. why pay this person this much money when we can get five people? Five bodies with a pulse. [33:23] James K: Like I love QA is great. And I feel like when I, got hired at raccoon logic, they were like, Hey, yes, you're a designer, but also could you do some QA? I'm like, yeah, man, it's fine. Like, I like it. Like, it's not a bad job. [33:33] John: Well, it's funny. I feel like at a small team at a small shop, everybody does a little QA, [33:38] James K: yeah, everyone does a little, but there's things like running daily smokes just to give the health of the bill that people can then like a backlog of, and they'd be like, Hey, well, they build those great two weeks ago. Why did it start being crappy? And then I can be like, well, that exact build number that we tested on had this change. So we can look quickly and start seeing what, what broke. Right? [33:56] John: Supervisor. [33:57] James K: whereas yeah, everyone on the team could check their stuff, but you want someone on the team to be giving you guys and gals and people the info. Right. [34:05] John: Yup. [34:05] James K: So, yeah, I just, I feel like it sucks that we don't get enough respect because we just doing our best. [34:10] John: Hell yeah, man. We're all doing our best. And that discipline is as essential as any of the discipline in making the games that we get out. We cannot be done without that discipline. [34:21] James K: and I love it. Honestly. It's really fun too. If you get a good team, [34:24] John: Yeah. Like that Metallica team, bro. [34:27] James K: Metallica team was fire the whole team the whole time I was at typhoon. I never thought like, oh man, I'm only a QA. I want to get out. But I was also in school to be a designer. [34:37] John: Mm. [34:38] James K: and they saw me going to school every day and my lead came up to me like, Hey man, do you want to do some design? And I was like, God, I don't know, man, you guys are, there's like only four of you. And you're really good. Like I'm just in school. They're like, okay, well how about we give you something small? Like. Okay. And at that point I was already fixing bugs myself. Like I was a very strange QA who would just, I had access to the editor. So if I saw an art bug, I would just fix it and then submit it. [35:01] John: Was it unreal? [35:02] James K: Yeah. It was unreal [35:03] John: Yeah. Which makes it super accessible to jump into [35:05] James K: oh yeah. So they were like, well, you're already in the engine fixing little bugs here and there. how about we just, give you something small to work on. And they're like, nothing crazy. Just like we're adding these collectibles that we don't really have many around in level. Just start placing them and like, you know, submit it, have fun. that's yours. I was like, okay. And I was like, [35:23] John: was typhoon, [35:24] James K: I wear like 24. [35:25] John: man. You see there's something to be said for themes, right? Anything under 40, because. These opportunities for growth, exploration learning, right? Or just like so plentiful that you get these opportunities that you very likely would not get at a huge AAA [35:43] James K: Oh, 2000%. I remember just, I showed interest in like, what was it? I was like, Hey, this enemy's kind of cool. How does it work? And the guy who made the creature was like, oh, you want to know how, how this works? I'll show you the behavior trees. You want to mess with it. I'm like, what? And he's like, here, like this, one's not done, have fun with it. Like you can submit whatever. It's not gonna be more broken than it is. I'm like, okay. then that got me into playing with. [36:10] John: Boom. [36:11] James K: I'm no AI designer, but I got to tweak a lot of them and it was fun. And it was just little things that every time I would show interest to someone, they were super ecstatic to tell me about it. Cause again, we're small and they have time And they're like, Hey, do you want to know how to do it? Cause I can use a bit of help, but if I teach you how to do it, you can give me a little bit of help. I'm like, Yeah. man. [36:29] John: Strategic, bro. How do you feel about offering behavior trees? Talk to me about exposure to them. How intuitive are they? What you like, what you hated, what didn't make sense. Just cause I have to talk to people about these from time to time and I always want to understand how I can break them down better [36:46] James K: I mean, they scared me looking at it at first because some of our creatures were a little all over the place in that. [36:52] John: 50 leaf nodes. [36:54] James K: Yeah. And I was like, man, I don't wanna touch that. But some of our very simple ones where it was very straightforward, was easy to just drag and drop behaviors that they made connect things up, testing. It was super easy. I wouldn't want to mess with bigger things. they, just looks intimidating. I feel like if I did it, maybe it wouldn't be so bad cause I do it. But I found the behavior tree and pretty simple at a base level. [37:19] John: fair. So start people off small, [37:21] James K: Oh yeah. [37:22] John: and then kind of stair step them through it, right? Like, okay. Here's the next guy? Here's like the [37:27] James K: Hundred percent. Right. cause if you throw someone in with anything bigger than that, and they've never seen it before, it's just going to look intimidating now. Again, some people love. But for me, that was like, I don't know about that. they're like, okay, here's the simplest enemy. I'm like, oh, I understand that. [37:41] John: yeah. Yeah. regular. [37:42] James K: then I can understand it and how it works really easy. I'm like, oh, okay. This node does that. And if I tweak these parameters in this node, I exactly see the outcome very simply because this enemy only does one thing. [37:52] John: Yeah, bro. Can you believe that behavior trees have been around since what? Like mid two thousands? I think they came out on the scene since like, Hey, little tool or something and they're used everywhere to this day, bro. [38:04] James K: Yup. Yeah. I know. [38:06] John: All right, James, I need to know about your story, man. Like how did you come into the game industry? [38:13] James K: It's not that exciting, but. I think when I was like 18, I had a friend who was working in QA and I messaged him one day cause I was playing gate, dark Alliance too. [38:23] John: Okay. [38:23] James K: I kept, breaking that game was pretty buggy on the two. And broke it a bunch and I was just chatting to him about it one day. Cause he was like a friend we were playing like I think we were playing wild together. [38:33] John: Yeah. [38:33] James K: And he was like, Hey, I just got a job at this company called VMC. Do you want in they're hiring right now? I'm like, I dunno, man. He's like, well that's cool. Like you're breaking the game already. Come get paid to break a game. I'm like, all right, that sounds cool. And they sent me like this really weird test where it was like, Hey, we're going to show you this 32nd video and tell us all the bugs. And I was like, all right, man. [38:52] John: off a video. [38:54] James K: I watched this, I don't know what game it was, but it was super weird and buggy and it was basically like a QA bug they found. And then they were like, Hey, just tell us what bugs are in this. And yeah, you had to get X amount. Correct. And you got the job and I guess I did. So I started working there did that for a lot. I think I was there for like five, six years. [39:14] John: Dan, that's a good one. [39:15] James K: Yeah. Then I was like, I'm going to get out of QA. Cause we don't get paid money in my, my work is scary cause I'm constantly like on-call and fearing for my job. [39:22] John: How common is that to be at that place at that time, for that long, it seems like you're like you have to be 20% to stick around that long. [39:30] James K: yeah, I mean back then there wasn't like as many people as there are now and I was giving it my all man, I was just wanting to be, I want it to be like a senior or a lead there, but there was just never positions open because there were so few of those. So eventually I left that studio and then I, was another studio in Montreal called enzyme and they were like, Hey, don't have like an office that we're gonna put you out, but we're going to put you in a store. And I was like, all right. So they embedded me at WB. [39:55] John: Yo that's right. felt like enzyme sounded familiar now. [40:00] James K: Yeah. That was like the big QA house that was helping to be, be for a long time. And I think now that they're key words, there there's that now, but yes, I was there and it was great. And then getting to actually devs around and, know, chatting with you guys during lunch and stuff. It Was pretty cool. [40:15] John: Was there anything that surprised you once you were in house, like compared to what you imagined games or like when they were in development? [40:22] James K: I mean, I didn't get to see the much, we would get to see like teaser trailers of what you guys were working on downstairs and stuff, but I just wanted to see more, but because I was like an outsourcer, we just were allowed because of our, how our NDAs worked. they eventually worked my way up to just working at WB, then gave me access to come down to your floors and see your stuff. [40:40] John: Yeah. [40:42] James K: Cool. And then I was like, Oh I want that. And then I met a great person named John Diaz [40:47] John: Oh shit. That's me. [40:48] James K: yeah. And he inspired me to become a designer. Legit. True fact [40:52] John: Get the fuck outta here, bro. Like [40:54] James K: working with you you were Like one of the first people who really made me want to go into design. There was another person, there was a, it was you and Jeff champagne. [41:02] John: shout out to a sham playing. I think that fool was like creative director on that, like and dragons game. [41:08] James K: the new, Boulder's gate. Dark Alliance. [41:10] John: Yeah. It all comes full circle, [41:14] James K: Yeah. No, but like it was you YouTube. Cause you didn't, I don't know. You were just so different with how you interacted with us. You guys were both super, just friendly and it really made me love the design side cause like, man, Sit down with either of you and check out your work and stuff, or JF would make me play test his levels. And and it was just super fun. I loved it. [41:32] John: remind me where that was, man. So that was already, I think. Post Metallica. It was like Sabbath or got them nights now. [41:41] James K: Yeah, it would be, it would be like the, the early, early, early days of Gotham night, like in its prototype phase. [41:47] John: Okay. And if I remember correctly, we were all in the same pod or strike team and we would be in stand-ups together. [41:53] James K: Yup. [41:54] John: I forgot how it was, man. I don't know if we had like a morning one and then the evening one [41:58] James K: I think we just had a morning one. And then like, well, there was a morning design one, and then there was maybe the sub-teams that you had an AI one specifically, um, that would break off. Yeah. And then JF, I think had like a missions one, cause he was on the missions design team. [42:13] John: Yeah. The crime scene, I [42:14] James K: Yeah. And yeah, I mean, it was just super cool. Cause I'd get to be in all those meetings. all you guys. And I was like, man, this is just super fun. [42:21] John: I need to ask you because I want to make sure that I keep that essence and that I keep that energy. What did I do so that I can keep doing it? So I will cause like you said, man, you in there kicking ass as a designer now. So I want to know what I did so I can keep doing that thing. [42:35] James K: I think you were just being you man. It was it wasn't no corporate Diaz. You know what I mean? Like [42:43] John: Yeah. You ever watch wrestling, [42:44] James K: yeah. [42:45] John: this makes you think of what are they called, man? The, the Alliance, [42:50] James K: Oh yeah, yeah, [42:51] John: the fuck it is. Right. You know, they wear a suit, they bring the briefcase out [42:54] James K: yeah, [42:55] John: corporation that used to work with McMahon, [42:57] James K: you didn't feel like that. Right. And some people, some people were like super siloed and they didn't really want to talk about their stuff. And if I would ever come up to them with, like an issue, they would kind of take it as like an insult, almost like how dare I criticize for design. Right. But some people aren't good. [43:12] John: Yeah. To be fair, It took me a bit to load. Right. This goes back to kind of the, I don't want to check something in. I haven't like dotted all the I's and slash all the T's and haven't checked all the possibilities. unsure, I'm insecure. I'm not ready to be criticized, you know, what we learn is fuck all that. While trying to make a good game, the sooner you get it in the faster we can iterate, right? Like everybody knows it's going to not be perfectly. It's going to be broke as hell. Right. [43:40] James K: And, I think you and Jeff were just the most real people on that team. And I felt like anything I would come to either of you with you, you actually actioned on or would take me seriously, right? [43:50] John: you know, you, a veteran bro, you got saw, you got great eyes. [43:54] James K: Yup. [43:55] John: for how games should work. Right. Or when things are off. Right. So it would be stupid of us not to have listened to you for sure. [44:02] James K: but just a lot of people, don't a lot of people don't I find, I find more designers do. [44:08] John: Okay. [44:09] James K: It's harder to get through to a lot of the programmers. [44:13] John: Interesting, [44:14] James K: because at that point I literally don't know the programming. [44:17] John: true, [44:18] James K: I just see there's a bug and then they're always like, well, it's not my bug man. Go away. [44:21] John: you bring up a good point to be fair. I think there's times where I don't get through to programmers as well, man. It's so you and I in the same boat, [44:29] James K: get it, most likely is not that person's fault, but somehow their system is interacting with something that's causing a bug. Right. So I just found that you and JF were just super down to earth and made me feel like part of the team a lot more. And didn't make me feel like I was QA in the team. [44:44] John: Okay. [44:44] James K: Right. You guys made me feel like. [44:46] John: All right. So the moral of the story there is make people feel like they're part of the. [44:52] James K: Yeah, Yeah. Just try not to just make them feel like they're not like, especially with QA, like just don't be like, Hey, QA person. Cause I've had people, I've had people say that on the teams like, Hey QA, come check this out. I'm like, man, I have a name. [45:03] John: Yeah, [45:04] James K: Like that's rude, [45:06] John: crazy. [45:07] James K: just, just nice to people. [45:09] John: Hell yeah, I like that. [45:10] James K: That sentence has to Be [45:12] John: Be nice. Don't be a Dick. There you go. What were you studying in college? Like for the design side, I'm curious what they were teaching you, what you were learning on. [45:23] James K: so my course was independent game design. So we learned a lot of stuff. we learned in unity and we had animation classes or art slash animation, but it tended to be more animation than we did. Design started at paper. We all had to build board games all the way up to, you know, make your own little Ferny sash games. So we made like a VR game. Then we had programming and like the last class was like a history of the industry and then how to self-publish yourself if you want to go into, [45:50] John: Well, like on steam or something. [45:52] James K: but, but more just how to, like, if you want to, how to kickstart how to get a publisher, how to promote yourself properly more of that. So, [46:00] John: that's pretty sweet, man. I didn't get that. When I went to my curriculum. Shit. [46:04] James K: yeah. Well, this was supposed to be a class two. If you want to be an indie dev, you have every tool. If you finish this course to publish a game. [46:12] John: Smart was Osama your teacher. [46:15] James K: No, but he was, he liked was the coordinator for the S the class. [46:19] John: Meaning what he like built the curriculum. [46:22] James K: Yeah, And you think, I think he was in charge of the teachers and stuff. [46:26] John: Yeah, I think [46:27] James K: But that was cool because I was also working with him at the time. I was like, Hey man, [46:32] John: Yeah, dude, [46:33] James K: I'm in this now. But he, he was great. [46:35] John: you got, you got, like free office hours while you're at work. [46:37] James K: Pretty much yet I got to use, I guess as much as I'm as I wanted, but yeah, so it was basically, you know, how to be a pure indie team and how to self-publish. And some people from class are doing that they're 100% making their own titles and they're, they've been working on it for like a few years and they're doing great. Whereas some of us, because of our teachers, our teachers were all like in the industry, there were from like Ubisoft or something. So it's, Hey, if you did good in that class, you know, your teacher will just try to, you know, help you get somewhere. Or we had a really good way to get mentors because you know, your teachers knew people in the industry, which was super. [47:11] John: What's the name of the school. [47:12] James K: This was a Dawson. [47:13] John: Gotcha. [47:13] James K: It was a short two. was great. It wasn't anything crazy. I would've preferred unreal over unity, but unity was cool because at least it forced us to learn programming. [47:22] John: The C sharp. [47:23] James K: Yeah. Cause you have to can't Do anything without it really. like that I would have preferred blueprint cause it would have been faster and I was just more comfortable with it, but I mean, unity was good to learn. [47:33] John: Do you think that learning C-sharp has made you a better visual scripter, AKA unreal blueprint? [47:40] James K: I still suck at blueprint? but Yeah. it did help a lot because at least I understand what's happening. [47:45] John: Yeah. [47:46] James K: A lot more than if I didn't like, cause I think before I went to school, I was like, man, blueprint looks confusing. I'm like, I don't understand anything. Then you get there. I'm like, oh yeah. Okay. I wrote that and I understand. Yeah. Yeah. It makes perfect. [47:58] John: I always have a sense that people jump into blueprint, prematurely, and if they were to kind of pseudo code what they're trying to build, you know, like, okay, I need the animation so that I can play it. And I don't want to stop it at this point, you know, on paper or as if they were writing C-sharp and then take that into blueprint. I think they would have a much better time, but, [48:19] James K: Yeah, the only thing I really loved about unreal is that if I wanted to get something done really fast to show someone an intention, I can just build it in the sequencer so fast. [48:29] John: Is that they're like little matinee cinematics tool. Yeah. [48:33] James K: good because if I just want to show you my intentions really quick, I can build something in the sequencer and have it all play out where, when I'm running into things, doing stuff, things happen. And I did no coding at all. I didn't touch the blueprint at all. I can do it. Minutes. And I can show you what I want. If you think that looks cool, then I can worry about actually making it so it works properly. [48:52] John: That's powerful, man. I mean, for people out there not understanding, right. I would give them the visual of, put me in a mocap suit with cameras where I can act out exactly what I want you to see. And it just loads up like instantly, right. [49:09] James K: Yeah. But on top of that, the sequence was also like, Hey, when I run into this trigger, what you just make a tiny little trigger that has like, when you enter in, which is the easiest thing you can do in blueprint. Right? You bet. Hey, when I do that, I want this wall to just vanish, to give the intention that like, Hey, I finally did the thing. I, or I killed the enemy. When I walked into the zone, the enemies die, which is me killing them. When I walked in this next zone, I progressed the wall crumbles. [49:33] John: Yes. [49:34] James K: to look, it's going to look rough, but like, I can show you what I want really fast. visually it looks nice versus like saying it to you, right. I didn't realize how much I love that until when we were doing some prototype stuff at stadia. And that was just so fun. Cause I didn't realize how quick I can get my design across without [49:50] John: Yeah. [49:51] James K: jump into the blueprint. [49:53] John: Walk me through getting the offer at typhoon. What was the interview process like and how did the opportunity for you? [50:00] James K: I think I applied to typhoon when they went live. So like when we were at WB, I applied for them when I saw their studio come on line that I heard nothing. And it was like two years later. And then randomly, I got an email from from Reed the because he was the CEO I think, or at least one of the founders. Yeah. [50:18] John: president of Warner [50:20] James K: Yeah. And then he, he basically ran typhoon and he was like, Hey, saw you were applying to be the, the lead come in for an interview. And I'm like, all right, [50:29] John: two years later. [50:30] James K: Yeah, it was out of the blue and cause I think at that point I forgot, I even applied. [50:33] John: Sure. The after that much time. [50:35] James K: Right. And then I went in and it was really just, they knew who I was already because worked at WB and read remembered me [50:42] John: Yup. [50:42] James K: which surprised [50:43] John: You remember who guy, man? [50:45] James K: Yeah. And then it was some other people who were there most, like a lot of the team I had worked with as well, they were either artists or programmers or just, you know, people who I've worked with in the past. And they were like, Hey, yeah. So have you worked in a real mic? Yeah, it did it at a WB. I've done it a bit at this other studio. I'm like, yeah, I've been working with that. Like, all right, cool. I'm like, I'm going to school. Like, that's totally fine. I'm not going to be designer like, great. You want to fix bugs? I'm like, yeah, sounds great. They said that as a joke and I did it. But that was pretty much it. And then they gave me an offer. [51:12] James K: They're like, how does that sound? Like, it sounds great. Like, I'll take it. And they're like, all right, well, we'll get back to you if have you got it? And I think they, they messaged me back like two hours later. That I got the job and I was like, That's crazy. [51:23] John: That's what something, man, like same day. Boom. You got to. [51:28] James K: Yeah. Yeah. It was nuts. I think it really helped that everyone there knew at least who I was, um, [51:33] John: you know, that's something we're talking about, right. To people listening in is the importance of your rapport, your relationships, fostering those, [51:42] James K: burned bridges, stone tone ever. It doesn't matter what anyone says to you. Don't don't ever stoop to that level. Just always be nice. Just cause people are going to remember you [51:51] John: you know by the nature of what we do, right? As creative, you open yourself up to criticism, you gotta [51:55] James K: Um, [51:56] John: people, not always gonna like what you do and tempers are going to rise, right? When things are [52:00] James K: oh, of course. [52:00] John: right, we're gonna get into arguments, my buddies call it creative discussions. But that's not what we're talking about. We're talking about being a human, being able to get your emotions out and apologize or. meet up and however you unpack that, right? Like, Hey, let's have a tea, let's have a coffee, let's have a drink, whatever. [52:20] James K: Yup. So yeah, that really helped. yeah, that was, it was crazy. Starting there was, was crazy because I don't want to, I'm not saying this to throw shade at nobody. All right. But the other, the, the old lead there just was very different from what I would've done. So when I came in, I think it was like they're like, Hey. Yeah. So here's what the lead did for a smoke test. I'm like, awesome. Like how often do you guys want it? They're like, well, I mean, like once a day, Okay. And I looked at him like, that's pretty short the games, not that big, my art. Cool. So I burnt it up in an hour and they're like, you're done like, yeah, like, oh, okay. [52:51] James K: And they were confused. And I did like four in the day and they're like, wow, how are you doing so many? I'm like, man, your game is small. You don't have many features yet. Like, it shouldn't be hard. [53:00] John: Yeah, [53:00] James K: but I also think it's just, I know how to do that. Well, because I've done it so many times. And I guess I don't, I don't realize that when I'm doing it and I, yeah. And I was able to blitz through their stuff. And then I made a way bigger, robust smoke for them with so many more things, which they didn't think they'd be able to have tested in a day. And I was like, I'll do it three times a day. And I'm like, get you one early morning by like 9:00 AM. It'll be done. They get you one from noon. I'll get one right before the end of the day. So you can have a history of how your check-ins are going. [53:26] John: Yeah. Cause I imagine the more smokes you have is a better indicator or a better way to create. What has broken, right? If you do [53:34] James K: Yup. [53:34] John: day, then you have 24 hours of check-ins to kind of [53:38] James K: Of course. [53:39] John: do three, the window is much smaller. [53:41] James K: Yeah. I can tell you, Hey, the game is super stable at noon, and then it stopped being stable at five. it's not something that happened early this morning. It's something that happened between noon and five. [53:50] John: and that's great to know. [53:51] James K: and that's why I was like, it blew their mind that I was able to do it. And I was like, well, I mean, I built it myself, so I know how to do my runs perfectly. I know how to manage what I do in a smoke. I can get the best out of my time. So if it's like, Hey, I got to make sure I test all the abilities against every creature. I'm also going to test, you know. the metrics at the same time. I'm gonna make sure I'm running and jumping as I'm burning through your level. Cause also gotta make sure all the levels work fine. I'm like, I'm just going to build myself this crazy course that I can run through to make sure I check everything in one shot. So. [54:19] James K: Running through the level. Okay. Level works. Okay. Now I'll go check the creatures. Okay. The creatures work. Okay. Now I'm going to check the, the three CS. Okay. Those work, like make sure I do it all in one shot. So I don't have to go back on myself. [54:29] John: Yeah, was it when Google came into the picture and says, Hey, you want to be a Googler? Here you are. You're a Googler now. [54:36] James K: Yeah. That was weird. I mean, it was cool going away from building three. Well, more than three skews of things to just having the idea of having one sounded super appealing. [54:46] John: Oh, because you guys became first party. [54:48] James K: yeah, we were the, we were the first party. studio. I think they would think there was another one, but, but yeah, we were pretty much like a big first party and this was my first time working as a first party dev, which was super cool. So it was, yeah, our game was going to be stadium. So it's one thing to worry about, which really takes headaches off of so many things. You know, I don't have to worry about testing the PlayStation, the Xbox and PC and the switch. right. It's just, stadia. Yeah, it was cool. I liked it. It wasn't, it was a lot of meetings and you know, [55:19] John: I hear this. one Scougal comes it's it's becomes a lot more processes and [55:24] James K: yeah. I mean, I feel like I don't know how it was for you to Amazon, but I feel like that's just how big companies are. [55:30] John: Amazon was similar. I found [55:32] James K: Yeah. [55:32] John: a lot of writing, a lot of reporting, a lot of data and a lot of check-ins man like validating any crazy decision or assumption writing games. There's a lot of gut in games, Amazon and Google don't operate off the gut. [55:47] James K: No. I mean, I didn't see it that bad from my side. Cause again, I was just a designer, so I don't know what my bosses saw, but for me it was more just Google specific meetings or Google specific talks we had to go to because it's just Google wide things. [56:01] John: okay. [56:01] James K: there was just so many of them, but I think it was also because it was COVID. there was this bonus layer of just weird at the studio. [56:10] John: There's a lot of learning, right? Like just information, sharing, knowledge, gathering, [56:14] James K: Yeah. And because like, you know, we're a small, we're a small little game studio. We know how to make games. It's fine. But I feel like meetings weren't for us, they were for the people who have never thought of working from home because they need to be in the office with other people. [56:27] John: That's right. [56:27] James K: up with it because we were part of Google. So it was, it was a roller coaster, but I liked it on it. [56:32] John: You liked it. You go back. [56:33] James K: I don't know, because the thing is like, what, what would I go back. to? Is there, is there games to go back to if it's, Hey, it's a thing it's stadia. Sure. But I mean, I couldn't do anything else at Google. I ain't no programmers. [56:44] John: So here we are today, raccoon logic just opened up and you guys got to re-acquire your IP. I thought it was going to in a Google volt. [56:53] James K: So did I? Yeah, it's not. I mean, we have the IP, who knows what that means, but we have it, which is, you know, a big leap forward, the not having it. Right. It's going to be, it's going to be nuts. And at least this time I get to be more design than QA, at least, which is going to be a big. [57:08] John: Talk me through that. Right. Talk with you. You get to live kind of the best of both worlds, essentially. Right? You get to do the thing, you know, and love as well as flex new muscles. [57:17] James K: Yup. [57:18] John: from pros and be able to bring your own juice to it, to the project. That's a designer. What do you enjoy about designing? [57:27] James K: That's a great question. I just like building stuff that people get to enjoy. And I haven't done much design, like I've said, like I've done a lot of collectibles and secrets and stuff, and those are super fun because I then go, when I jump on Twitch and weirdly people still playing that game, [57:42] John: Yeah. [57:43] James K: people like the journey Savage planet, and I love watching them interact with my content that I. [57:48] John: Yes. [57:49] James K: fun. Like, Ooh, do you actually like my quest? Cause people at work tell me they do, but is it really good or it's Ooh. Did you, did you find that collectible, that I'm walking, I'm watching you come up to like, do you find it entertaining? You know, I'm, I'm sure as I grow and get to do bigger and better things, just going to be even more of a fun feeling afterwards. But right now, like it's so enjoyable doing that. And that's really what I want to keep doing. I just like, it sucks games takes so long to make. [58:16] John: Yes. [58:17] James K: But that's all I want to see. I just want to see people interacting with the content I'm building and just, you know, see what happens. [58:22] John: I like that, bro. And the F for sure, all the streamers out there, we get to get that feedback like right then and there, to either things that we can only see on the dead floor from, from our own team. Right. And we're all kind of to be fair, we play it a certain way. people in the, in the wild play very differently, you know, in a way that you never could have conceived of on your own. [58:42] James K: Oh, yeah. Well, trust me. I, I know, but you know, it's interesting. I was interviewed for a speed run, thing for IGN. They did a speed run of journey Savage planet. It was like me, Alex and our community manager, Dennis, [58:55] John: Alex Hutchinson [58:57] James K: yeah. [58:57] John: Community managers, dentists [58:59] James K: But yeah, it was, it was awesome because they were like, oh, does this hurt you to watch people break your game? Like, no, I find it so fascinating. and they're like, well, you're the QA. You don't find that weird. I'm like, no, this is the best part. Like the games I'm breaking, they're able to beat it. They're doing it like 12 minutes. It's so. [59:14] John: the. [59:15] James K: we didn't want to fix it internally. One of the. speed runs did get fixed, but we didn't try to fix it. It just so happened to be like a an autogeneration of like LDS that broke something. And then when it got fixed, it sucked that it got fixed, but we weren't trying to fix it. We don't want to, take any fun away from the speed runners. Cause it was so cool to watch or like, how cool is it that someone is dedicating so much time beating your game the fastest, right? Like that's just cool. [59:41] John: helps the game live on to be fair. Right? There's this whole world of speed runners trying to min-max and learn how to be pixel perfect at a game. [59:50] James K: Yeah, So for me that was just like, oh, super fun to watch man. And that's what I want to see more of, like from streamers as I start doing more design, like I just, I just want to see people engage with it. I don't care how you do it. Like you want to speed, run it, have fun. I love it. You want to show me how you can break that thing? I spent a year making do it. Like it's just going to make me grow as a designer. That's all. [1:00:12] John: just like QA has so many different branches to does design. Is there a particular area of design that intrigues you the most? Or where do you see yourself? Like five years from now as a designer? Where would you like to be? [1:00:27] James K: That's a good question. At the moment. I'm just kind of vibing with like a generalist designer. I know, I know I don't want to be a level designer. Systems design sounds really fun. AI is. intriguing a little intense. I don't have the, the, John Diaz mindset. thanks. I read it, but yeah, it's, dunno where I want to be yet. I haven't had enough time to play around. [1:00:50] John: Okay. [1:00:50] James K: I just know that when I watch people do level design and I'm like, that is never going to be me. It's [1:00:56] John: that's a big learning point, right? No, the thing that is not for you, that's a huge learning point. [1:01:02] James K: I love seeing it and I love seeing people who can do it well, because it's so cool. But my brain does not work like that. [1:01:09] John: for sure, man. Like a game is only as good as the space you get to kind of create in, you know, [1:01:15] James K: yeah. That's, that's the only thing I know I'm not going to do and watch five years, I'm going to be a level designer would blow my mind, but [1:01:21] John: to be there. You got [1:01:22] James K: yeah. Yeah. But it put Noah it's I dunno. So far just a generalist, just having fun or poking a few systems. That's always really fun to do too. [1:01:31] John: What was it about raccoon logic that Lord you in it? [1:01:35] James K: The team a hundred percent. [1:01:36] John: This is mostly the same people you work with at typhoon. Yeah. [1:01:39] James K: Yeah. I just with them so well, gave good freedom to what I wanted to do. Right. These are the people who let me go from just being the QA lead on their team to wanting me to become a designer on their project. Right. Like I remember anytime we go to like a San cassette, it was always like, man, we're so happy you're in school. You're gonna make such a good designer. I'm like, oh, that's awesome. So it's, it was always that it's like, these people are just so fun to work with. I can't wait to work with them again. And that's why it was really sad and Google shut down because they were just so fun to work with. They make really good games to make fun content, but they're just good people. [1:02:11] John: a group of people that believe in you that want to see you grow, that are excited to work with you [1:02:15] James K: Yeah. [1:02:16] John: for what you bring to the project. For sure, man, you want to vibe and rock with those people? [1:02:21] James K: Yeah. So that was, that was really it. Like, why would I not want to be with that team? Right? [1:02:26] John: I get, it makes sense to me. Hi James. I'm a hit you off with the lightning round. You ready? [1:02:33] James K: Yeah. Go for it. [1:02:34] John: What's the last game you finished, [1:02:36] James K: I think it was the new ratchet and clank game. [1:02:38] John: Oh, that's a good one. [1:02:40] James K: Yeah, What is it? Rifton timer or something? [1:02:43] John: Yeah, you can get a lot of [1:02:45] James K: rift apart. Yeah. And that's one of my favorite studios period. insomniac. They make such gorgeous games, but I think that was the last one I finished. I've attempted to beat a lot of games, but that one sucked me in over the weekend that I couldn't. [1:02:58] John: That's why this question is pretty powerful, man. Like those, all the options that we have on how to dedicate our time. It's few and far between the game that compels you to complete it. [1:03:07] James K: Yeah, [1:03:08] John: Dope. What's the last book you read? [1:03:11] James K: It was called the art of game design. [1:03:13] John: by Jesse shell. [1:03:14] James K: Yep. That's the one [1:03:16] John: yeah, that's a good. [1:03:17] James K: S as a big boy. Yeah, that was, that was the last book. I think every designer told me I just had to read it. [1:03:23] John: Yup. Yup. That guy [1:03:26] James K: yeah, I think I read it during school. [1:03:28] John: anything that still persists in the memory from that book [1:03:32] James K: No. [1:03:34] John: you applied day-to-day [1:03:36] James K: I, I, think, I think it, it, did change the, way I did design, but, how I could not tell you, [1:03:41] John: how are you liking this whole work from home thing? [1:03:43] James K: Honestly it's not bad. I do miss being in a group of people. I mean, like working as a small studio is so much easier to just run over to someone's desk and show them something and work with them quick, then having to see if they're online, see if they're not in a meeting already. That's the only part I don't like about the work from home is how hard it can be to actually chat with people. [1:04:04] John: Yeah, you got to book it. It's gotta be in the calendar. Yeah. Most of the time. [1:04:07] James K: And that sucks. Cause I was so used to just walking over to a desk and talking to someone. So Besides that if that somehow gets fixed, I would love it, but don't, I don't hate it. I just don't like being able to actually chat with people properly. [1:04:19] John: What's your ideal situation? Is it like a hundred percent in the office? A hundred percent at home or some type of hybrid. [1:04:24] James K: It's the hybrid. And I, believe that's what we're doing at rec and logic. I think we're doing a, three-day in office two day at home. So you schedule all the big meetings in the office you know, do all that over a three-day period and then you have, you know, I think it's, I don't know what days it would be. Let's say it's Monday, Friday at home and then Tuesday, Wednesday, Thursday in the office. Right. [1:04:42] John: Where's the. [1:04:43] James K: it's on St. Laura and Rachel, so down near the mountain. Yeah. [1:04:48] John: Oh, snap. [1:04:49] James K: But yeah, so that, that's my deal. A few days in the office, a few days at home [1:04:53] John: Okay. [1:04:53] James K: with the, ability to, if the weather is horrible, not come in the office. [1:04:58] John: Yes. In the winter. [1:05:00] James K: yeah, Montreal winters is cold, [1:05:02] John: Yeah. [1:05:03] James K: all. And I think that's the big thing that worked from home did is give us the ability to say, Hey, like it's bad. I can stay home. I can still do my job. Right. So that's my ideal, a few days in the office. But with the ability to, if reasons I don't have to go in [1:05:18] John: okay. [1:05:18] James K: work [1:05:19] John: What would you be doing if you weren't doing this? If you weren't making games. [1:05:23] James K: well as I got my first job in the industry, I also was applying to go to school back then at the exact same time. And it just so happened. They both happened at the exact same week. So it was, I got acceptance to school, but I also got the job. I took the job. I was going to go into learning to be like, I'm a systems administrator for PC. [1:05:41] John: CIS admin was, so what's the, what is that? Is that like standing up racks and managing networks and stuff like that? [1:05:50] James K: And like also it, [1:05:52] John: Yeah. [1:05:53] James K: worlds, I fascinated with computers. So that's what I wanted to go into. [1:05:56] John: That's a, that's a cousin of what we do, [1:05:58] James K: yeah, I had had both options and I decided to go with the, the game one, cause it sounded cooler. [1:06:04] John: yeah, you could probably do that for [1:06:05] James K: Sure. [1:06:06] John: Did, they give you an opportunity to like transfer to another team? Okay. [1:06:11] James K: were really helpful, but I mean, most teams are program centric. There's not really When you say the word design, it's more about being like a graphic designer [1:06:21] John: Yeah, product [1:06:22] James K: or like a web designer. I'm either of those, [1:06:26] John: Yup. [1:06:26] James K: but they were very helpful. [1:06:28] John: Okay. [1:06:28] James K: I have no ill will with these people at all. They were great and they did try to help as much as they could. It's just, stuff and I think. Even if there was a job, it was you'd have to move to the states. And I really didn't want to move to the states. [1:06:38] John: They were getting damned. They were getting completely out of Montreal. [1:06:41] James K: Well, nobody is. Cause it was more like what job you go for dictates where that job is. Right. So it's like, Hey, let's say, let's say I found a job. And it was like working for X division. If that division is in California, I have to go to California [1:06:53] John: Yup. [1:06:53] James K: because I know they still have stuff in Montreal, but those are very programmed centric jobs. So anything designing, I think was more in California or in New York. And Yeah. those places sound expensive. [1:07:04] John: yeah. Oh yeah. Oh [1:07:05] James K: So that was more the reason for not wanting to do that. But yeah. they tried, they were nice. [1:07:09] John: I, so closing this episode out, we try to leave it a little better than the way we found it. What words of wisdom would you impart on us as an industry? What could we do better? Right. If you had a wish to wave a wand or on a genius, something, what would you change about the industry? If anything, [1:07:28] James K: I mean, the only thing, and I, this is again from the QA standpoint, I guess, is just treat QA, like people and give them decent salaries. And don't give them like one week contracts where they're constantly on call and fearing for their jobs. Right. Because like, we help your games. [1:07:44] John: Oh, yeah. [1:07:45] James K: Like that's all there is to it. Right? So for me that, that's it. And I think I watched one year, there was a, a GDC conference from BioWare Montreal, and they had a dev QA conference. And they're basically saying, it's like, Hey man, where your, where your armor, like where the studio is armor and your shield like use us to your best. Cause this is what we're there for. We're There to protect you guys as much as we can. Right. And that's all like, just treat us like people, [1:08:10] John: I [1:08:10] James K: that's all. [1:08:11] John: I like it. I that's a message that I can easily carry forward and propagate in my little daily activities. [1:08:17] James K: Yeah. [1:08:17] John: What do you wish you knew? Or would you go back in time until younger James Kane? Maybe like mid nineties. [1:08:26] James K: Mid nineties. You can work in video games one day. [1:08:30] John: Are, you didn't know, it was even a thing. [1:08:32] James K: No, man. and it's crazy. Cause I see things on like I see like you do videos of like all the tare QA. And I was like, I never even knew that was a thing. [1:08:40] John: Yeah. [1:08:41] James K: I just thought these games got made and came out somehow. And like did not think there was a QA point to this. [1:08:47] John: It's funny to me, Jane is because I grew up in New York and there was very little game dev in New York. Right. Everything was happening in west coast or in Texas or something, but Montreal is such a huge Devon man. Like can't go to a bar and not bump into a [1:09:03] James K: Yeah. But, but were they in the nineties though? [1:09:06] John: Fair. [1:09:06] James K: cause now yeah, every game studios here in some way, shape or form, like everyone's here, [1:09:12] John: for the nineties. [1:09:14] James K: Yeah. But I also thought back then that you had to be like a programmer to be in the industry, right? [1:09:20] John: or a programmer. [1:09:20] James K: Yeah. I always thought that was, that's what it was. [1:09:23] John: Yeah. [1:09:24] James K: So I just never thought it was a thing. And I think that's why when my friend brought it up, I was like, man, I can't do that job. But like, okay. Maybe I can, like who knows? [1:09:31] John: why I'm putting the show out there, man. somehow some way you don't think that there's a job for you in game development, that's what I'm [1:09:37] James K: Yeah. [1:09:38] John: and putting them on and sharing this podcast for [1:09:40] James K: And like, if I can tell. I don't know, early two thousands. Me, when I was in the industry, it would be more like don't be afraid to go Indy. It's not the end of the world. [1:09:49] John: Like go make your own thing. [1:09:50] James K: Either go make your own thing. or go work in a smaller company. Like, cause those were always scary, man. It was always like, well I have to stay AAA because of job security, [1:09:59] John: Yeah. [1:09:59] James K: but indie make pretty cool stuff and you get to juggle more hats than you would at the AAA. [1:10:04] John: Yeah, like we mentioned earlier, right. You just learn so much more and you make yourself that much more employable. [1:10:11] James K: Yup. So that's more what I would tell myself. It's like, Andy's not terrifying. Cause typhoon was a risk because it was an indie studio and I was going from a job at a AAA that was secure to an Indi. But yeah, it shouldn't be that, that scary. [1:10:27] John: No regrets, right? [1:10:29] James K: Oh, not at all. [1:10:30] John: Hell yeah. James, man. I love kicking it with you. You're welcome back any time. As soon as raccoon city has got some fun things to talk about once you to come back, want to bring Reed on the show. [1:10:42] James K: Um, [1:10:42] John: want to bring Alex on the show. Where can people go to reach you connect to, to see what you're working on? Anything like that? [1:10:50] James K: connected me, just go to LinkedIn, easiest place, sees these places to see what I'm doing and just chat. I feel like, LinkedIn is getting so much more popular these days. [1:10:58] John: is the shit, bro. [1:11:00] James K: Yeah. [1:11:00] John: It there's very minimum bullshit on there. At least on my feed [1:11:04] James K: I'll say. [1:11:05] John: It's [1:11:06] James K: Yup. [1:11:06] John: things I can love and it's all love out there, man. It's love, support and interesting conversations and ideas, [1:11:13] James K: Yeah. Yeah. So a hundred percent just go there. Message me if you want to chat. [1:11:17] John: LinkedIn is pretty much responsible for almost all the work I've gotten after my first gig. So [1:11:21] James K: Yeah, no, it's really, it's, it's so much better than people think it is [1:11:25] John: oh, so good. But I will link your LinkedIn in the show notes for people to click on and connect with [1:11:31] James K: dope. [1:11:32] John: We got a ritual on the show. I don't know if you've heard any previous episodes. If you have. It's if you had a good time falling out of the play area, kicking it with me. there anyone you would nominate to come on the show and fall out behind you? And this is someone that you think could make for a compelling guest, someone that you've looked at as a role model or just someone you think is awesome. [1:11:56] James K: I mean, get, get Jeff champagne on here. [1:12:00] John: Awesome nomination. I'm [1:12:02] James K: Get that, [1:12:02] John: happen. [1:12:03] James K: get that, get that boy on your, He's he's such a fun, fun guy too. [1:12:07] John: oh, he's the [1:12:08] James K: Yeah, get them on. [1:12:09] John: I'm a, I'm going to try to wrangle him, man. I know he's super busy these days, [1:12:13] James K: Yeah. [1:12:13] John: to make him happy and I'm going to be like, yo, it was not me, James tagged you, bro. [1:12:18] James K: Yeah. I mean, you, you, tell him that I'm down. [1:12:22] John: but James. Thank you so much, bro. Do you have any closing words for the people out there before we wrap up? [1:12:29] James K: I just Love QA man. That's about it. Like, [1:12:32] John: QA put, put the hearts up, [1:12:34] James K: yup. [1:12:34] John: on. Like there send a slack. If you hearing this, a message to your local QA, tell them how much you appreciate them. [1:12:42] James K: Oh, a hundred percent. No one does that, [1:12:44] John: there you go. You make a [1:12:45] James K: like you do that. you make their, their year. Yeah. Ciao. Ms. Diaz. [1:12:58] John: one of my favorite things about this show is just hearing the perspective of people who are coming on to dev floor for the first time. It's just so refreshing hearing the first time. Perspective, especially as you become a jaded veteran developer, we can forget what it's like, that we have pretty special careers and that we should not take them for granted. People would honestly kill to do what we do. And that's what I like capturing and sharing the insides of the industry. It's glamorous. It's tough. It's taxing, but it's so damn worthwhile. As long as you're working with great people who give a shit about the product and the team. I always say whatever you're doing, learn the engine or the editor take initiative to learn the tools and use them in whatever way you can to help the team. [1:13:43] John: The majority of the time, if you're learning and moving the needle, getting changes, reviewed, and approved and committed, that's going to reflect positively on you. And those are skills that you get to develop on the. There's very few things better than leveling up while getting paid at the same time, I've worked at places that seriously slapped my hand from touching systems that I didn't author or right. Even though it was a small enhancement that was buddied approved, tested and verified, dude came over with some, God complex was like, yo, don't touch that. No reason, no explanation, no discussion Russ, the shirt I never did. And I got the fuck up outta there. [1:14:18] John: Cause that's not the type of leadership that I want anyway. Man, you know, reminiscing about WTB games, monitory out. We had such an amazing pool of talent, such awesome people, super passionate, super creative I'm rooting for the people who stayed behind to pump out, got them nights. But for the rest of us that made the tough decision to leave and jumped. And go on to push out other games. I love connecting with them. If there's one guarantee in this wild industry, is that it's very likely that we may very well end up working together again someday. Lastly, be nice member James Cain's words. Be nice to your devs. Be nice to your QA. Let your fellow teammates and QA know today, how much you appreciate them. [1:15:03] John: And if there's any way that you can help make their life. Or even take an interest in how they want to grow and help foster that better teammates make for a better development cycle. On episode 28, debuting the week of GDC, 2022. I'll sit down with the speaker behind 1000 hours of difficulty. How destiny builds systemic challenge and a dear old friend and mentor in this tech design space, a fellow all to the. Alan Blain, a principal technical designer at Bungie working on old things. Destiny. We go through his vast journey coming up from Pasadena, working on Thrasher skate his time as an electronic artist at Westwood in loss. Working on warriors for rockstar Toronto, and then making the jump over to rockstar San Diego, where he was a huge part in building out that design team for that game of the year award winning red, dead redemption one, as well as helping us get our footing on GTA five and more. [1:15:58] John: make sure to follow us so that you don't miss out on that episode. Thank you for listening, Deb. If you found this episode informative, I ask that you pay a link forward to a developer to help grow our listener. If you're a game developer with a story you think could help a fellow dev out, please go to out of play area.com and click on the Calendly link at the top to meet up, please make sure you get approval from your manager or studios, PR HR team beforehand. Out of play area, the game developers, podcasts releases, new episodes every other Monday on all the major players, including Spotify, apple, and Google. Please make sure to follow us, to see what developer falls out of the play area. [1:16:36] John: Next time. I'm your host John Diaz until next time devs stay strong. Stay true. Stay dangerous. Mega ran. Bring them home.