Out of Play Area, a game dev podcast by John R. Diaz Ep 29: Jason Jurecka (Lead Software Engineer @ Visual Concepts) Published Mar 28, 2022 ยท 111 min Episode page: https://outofplayarea.com/podcast/ep-29/ Transcript (machine-made, lightly edited; may contain errors): [0:00] John: What's good devs after Inscryption cleaned up at the game developers choice awards and the homey Osama subjected us all to his never-ending puns that, you know he's been writing for way too long. And even with will Smith smacking the taste out of Chris Rock's mouth for mentioning his wife and getting a much well-deserved Oscar for king Richard. While those are great distractions. Let's not forget that there is a war going on in Ukraine that is still leaving shockwaves. I'm proud to say that the home team Epic has been donating proceeds from Fortnite since March the 20th running through this week to April 3rd to humanitarian relief aid for people affected. [0:39] John: As of last Friday, we raised 70 million us dollars. Let's keep it going. Additionally at the request of my guest on this episode. I'll mention that Jason comes onto the show to share his own views and solely his use, which do not represent that of his current employer or any former employer. Now hit my music. On episode 29 of the game developer's podcast Out of Play Area. We sit down with lead software engineer at Visual Concepts working out of LA who just released WWE 2K22 laying the smack down on the competition. He's a fellow Full Sail alumni whom I had the pleasure to work with at Rockstar San Diego on Red Dead Redemption 1 and GTAV. And he's worked with damn near all the heavy hitters in the game from Blizzard to EA working on Battlefield to where. [1:30] John: It all started at big huge games working on Catan and Rise of Nation Rise of Legends. On this one, we'll talk about. What day in the life, what it means to be a lead working on user generated content tools with WWE 2K22, we talk about what led him into programming from starting by tinkering with computer hardware. And we dive deep into burnout and unpacking that, and then talk about everything that goes into pipeline engineering, build resource management and all of that. Hailing from Weimer, Texas, please. Welcome Jason Jurecka Let's fall the fuck out. [2:10] 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 [2:34] John: You're actually the first pure engineer that comes on the show. I think I've had a few people that were engineers and then made the transition to design or production or other things. But you stay true to your roots. I always find a surprising I'm like, yo, why would you leave engineering? That's like the most money, most control, all the good stuff. [2:52] Jason J: Yeah. I mean, I have a kind of just love the problem solving that is presents itself. the day to day is essentially you're solving problems and that is something that's always been interesting to me. I have, you know, had a, an inkling of like, oh, if I make my own game, I'll be the designer and all this kind of stuff. And like, thinking about like how systems interact with each other. And then I start to kind of construct it and I'm like, man, I'll really want to write the code for this. So it turns into like building the programming layer as opposed to being super deep into the design. [3:24] John: I'm always interested to see how people find their passions because I always look at it like I can't do what you do and then you can do what a lot of us can. But you ended up gravitating more towards the code. So I liked that aspect of what we do in game dev. Like everybody has a superpower. [3:39] Jason J: there are things that I've been amazed by just having conversations with designers. Like I have crazy ideas, just like every designer does. And then when I start to discuss it with the designer, they come at it with many different perspectives and many different options. And I'm like, man, I didn't even think about that. several times I've talked with designers that have done interviews and they'll, discuss about what happened in their interview. And they'll be given like a task, like, Hey, come up with a boss fight [4:05] John: yeah, [4:06] Jason J: they'll like, go like, okay, well, what is the theme of the game? What is all the like, stuff that needs to happen in the boss fight? Like how many beats does it take to beat this boss? Like usually you'll have more than one form of the boss. You'll have kind of the initial one and then you'll cascade into, oh, this is the more urgent one. Or as the health progresses downwards, it's like, okay, now he does different moves or, you know, just seeing kind of someone's eyes light up and their brain just electrify when they start thinking about all the possibilities they could do there is really cool. I mean, I, I definitely do not have that spark that happens when I think about those types of things. [4:42] Jason J: I think that more of it as a, okay, I have a boss, so that means I need to have a boss that has a lot of HP, uh, or I have a guy that has a lot of. You know, varied attacks, but how they kind of interweave into each other is more that designer mindset that it would take me longer to come up with than some of the other people I've talked to. [5:05] John: have you ever done a design interview out of curiosity? [5:08] Jason J: I have not [5:09] John: How are engineering interviews? I'm always daunted by white board coding. You know what I'm saying? [5:16] Jason J: it depends on where you go. you know, in general engineering interviews can be asking you a bunch of, uh, asset Terek kind of questions that usually you don't necessarily deal with on a day to day basis. I've definitely had those questions where they ask you very specific, like, uh, syntax things about the language that you're programming in. And if you get it wrong, it's a strike against you. one that commonly comes up and is kind of on all the, like, prepare yourself for these interviews. Things is, invert a binary tree and for a lot of people in their day to day, they don't do that. and some of the, motivation of a programmer interview, Gotten farther into programming is to kind of see how they solve a problem, as opposed to them being able to regurgitate an answer. [6:01] Jason J: but a lot of interviews really have stagnated on kind of those very specific type of questions that are more formulaic. And they aren't actually like, Hey, I'm figuring out a problem. some of the best interviews I've ever had have been things like, Hey, we're going to solve this problem together. And either it's like the interviewee and the interviewer are solving the same problem. or if there's multiple candidates, you're teaming up with those multiple candidates and coming up with an answer [6:29] John: Well, that makes so much more sense to me because that's actually what the day-to-day job is versus a completely hypothetical situation, which, Hey, you're going to have Google, you're going to have your compiler. You're going to have IntelliSense and all that stuff to like, study or look up what you need to get the job done. [6:46] Jason J: And sometimes, maybe as your confidence grows in your ability, it's okay to tell someone like, I don't know, but I would look it up. Like, that's something that I learned later on, [6:56] John: that's a viable answer. tHAT IT is an actual viable answer [7:00] Jason J: Cause I'll just be, I won't try and be fake it. Like, I'm going to be very honest with the interviewer and say like, I haven't done that or I haven't heard of that. Or, I have dealt with that many years ago, but I have lost kind of the, the math, uh, algorithm that I need to use. And so I would have to look it up [7:17] John: it's funny. That confidence thing, for sure. When I was first starting out, I thought that I had to have all the answers and I have to figure it out. And if I couldn't figure it out, right. I was just kind of stepping through it and stumbling harshly. And then yeah, as you get more experienced, you can talk to, oh, I've actually never done that. This is how I might approach it but you end up asking more questions, right. Like to help clarify or do alternative versions of it for sure. [7:43] Jason J: sometimes I have definitely failed interviews by kind of saying over and over again, like, you know, sorry, I haven't dealt with that. Or I don't know that, like I had one interview with a company that they were more in the non-game sector and they wanted, me to basically build a, a dice role, kind of thing. [8:00] John: Okay. Let's do it. [8:02] Jason J: And I haven't done that. So they were like, Hey, so what do you do? I was like, okay, well, you know, I was like, we'll get a random number. And like, you know, I was basically stepping through it as though I was just new at doing these dice rolls. When you know, someone who's a gameplay in. Would have had a lot more exposure to like, okay, I'm doing random numbers and things like that. So they would have more knowledge on being able to like quickly come up with, alright, we have to do random number and then put these probabilities on it. And these kinds of modifications to it. And I didn't have it at my fingertips. So I was like, well, I'd have to look it up or I'd have to, you know, Hey, I haven't done that. [8:37] Jason J: My day-to-day hasn't focused on that. I didn't get offered the job, but at the same time, it's like, I was honest with them. And, you know, that's something that as I've gotten older, I've definitely tried to just be honest with them because I don't want to hide and say like, Hey, I know how to do all this stuff. And then I show up the first day and they're like, Hey, do this. And I'm like, uh, I've never done this. So just being honest is something that will get you farther than what then you think. [9:02] John: for sure. I can't imagine luckily getting a job and then you're not at all suited for the day to day. [9:08] Jason J: it is something that I've seen other engineers try and do. Like, uh, like you were saying, when you first got in and you were interviewing, uh, and if you were doing technical interviews, you're like, I have to have the answers. I have to have all the answers. And a lot of the Information about how to get a job as an engineer is about having all the answers. Like you have to know everything to the most minute machine level, just to even get the interview. When what you're going to be doing is editing HTML. my interview at rockstar was like that, like I was interviewing and they were asking me all kinds of questions about maitre CS and, data structures and all kinds of stuff. [9:47] Jason J: And I was answering them and then it comes out my, my job, my first day, it was like, oh, you're going to edit HTML. And I was building out like internal webpages to display, like build results or fix bugs in that HTML, when the job description didn't say anything about HTML and, you know, I was like, okay, well let's just solve the problem. And you know, it kind of worked out. I mean, they were surprised that I was fixing things, but at the same time, I was like, you know, you hired me to solve problems and that's what I'm doing, [10:17] John: It's funny for Roxanne was definitely grateful to not have been too far removed from my collegiate, like linear algebra and sohcahtoa and finding hipot nooses and thought products. And, [10:28] Jason J: cross product. [10:29] John: cross product. Yes. [10:30] Jason J: And that's, that's another thing that usually gets thrown out as default boiler plate questions. Like those types of. Right. The formula to do a dot product or write the form enough to do a cross product. And those are things that you can look up And as an engineer, knowing how to use it is what you're looking for, [10:49] John: yes, exactly. I've been able to survive interviews narrowly in mentioning, Hey, I don't remember the exact formula. I can't write it for, you, but I know that I would use the dot product to get me a valuable that lets me know what side of the thing I'm on or the degrees that I need to turn towards something. You know what I'm saying? Okay, cool. So given that, how would you use it to figure out that you got to point the camera over here at this thing that's shooting at you or something like that? [11:16] Jason J: Yeah. [11:16] John: Ah, so happy to be well, well, well removed from those days, [11:21] Jason J: That's one of those things where a little bit of knowledge can help. in my career I've been in roles where I've had to interact with content creators, and that's something that usually is a rough spot for engineers is they aren't able to translate their highly technical speak into something that a content creator is gonna understand very well. I've straddled that line my entire career and. Really liked it. Like, I really do like sitting down and talking with a character artists and looking at the textures that they're drawing and like how they have it set up from a artistic standpoint, as opposed to just the nuts and bolts of like how a texture is compressed or something like that. [12:04] Jason J: The same with designers, like sitting down and like saying like, okay, well, this is how the system is going to work. And like, how are you going to use it? And what would you like to do? And, you know, I haven't had those kinds of problems as far as I know. [12:15] John: that common vocabulary is so helpful, right? Whenever we can speak with you about some of the ways that we would approach what we're trying to do and vice versa. When you come sit with us, see how we're going to try to do something. I'm sure it informs how you build something out or how you architect it. [12:34] Jason J: yeah. And there is sometimes a miscommunication there [12:37] John: That will always happen. [12:38] Jason J: you know, there's what you say and what the person hears and then what they intend. And I've definitely been in that triangle where you're trying to like, make sense of what they're asking for, and then you try and interpret it and present them with, Hey, is this what you want? And then there'll be like, no, I didn't want that at all. And you know, so there is a give and take there when, when dealing with. [13:01] John: Miscommunications will happen. They will happen a lot, no matter how hard we try and type to each other and write emails and many layers of approvals, they're going to happen J so I have no clue where the heck you are at currently. What you've been up to all this time. Where are you at now? What are you doing? What's your role? [13:21] Jason J: uh, so right now I am at, visual concepts, LA the LA studio in Angora Hills. I am a lead software engineer, uh, working on all of the creation tools, for the, WWE franchise, [13:34] John: Ooh. [13:35] Jason J: the two K WWE. I'm building out a group to actually provide a tool set to content creators out in the world. it's a in game, but also kind of a tools thing, which is really in my wheelhouse. And I've done all the tool side from the backend side to, you know, presenting tools and editors to users and shipping those types of things. So this is really kind of a interesting, opportunity. I think of it a lot, like building out RPG tools. Like if you think of a Skyrim, you can customize your character a little bit. And things like that. the tool set that we're providing has a lot of options that are much more surprising. Intricate than what, I have dealt with when dealing with kind of like RPG makers and things like that. [14:18] John: Is it because there's just so many different parameters and things to tune and tweak and look at and select from [14:24] Jason J: yeah. and there's also multiple ways to interact with this. So not only is it something where you can create your own character, you can create arenas to host matches, you can create your own, championship belts. You can create like your own, shows, but it's effectively like, so if you saw Like Monday night raw or something like that, you can create your own version of that, where you set up the fighters and you set up the, the arena that it's going to be in and all of that stuff. So there's not only just character creation. There's like this universe of things that you're able to create. I have played a lot of sports, sports games, and I've only really played the, my player kind of modes [15:03] John: Yeah. Which RPGs, right. [15:05] Jason J: yeah, they're RPGs. And I've found that those modes are much more narrow in scope than the, two K WWE version is like, and I've played like the, MLB the show mode, and you can create your character and you can kind of customize a face and whatever. You don't really get to create like their outfit and you don't get to create the ballparks that you're in and things like that. I think, MLB 2021, this year's version does have a ballpark creator that you can use. and you can create a franchise type thing where you create a fantasy baseball team and then you can put it in a league, but there's a lot of rules that define that scope game. Like you have to play baseball. [15:45] Jason J: The field has to be a certain size, uh, and your player has to have a certain kind of normalcy about them. Like they have a face, you can't change their uniform. Like the uniform is, is kind of, is kind of static for that team. but in the WWE world, like all that stuff is kind of customizable and you can kind of create a character that wears all kinds of crazy outfits and kind of create arenas that, you know, given the templates that we have, you can create a Rina's that have different displays on it and videos and all kinds of stuff. So it's quite a expansive tool set. [16:19] John: it's been a while since I played a wrestler and I was such a big fan back in the Nintendo 64 days, and even some of the Def jam fighters. but Yeah. it totally reminds me about this crazy world of. I think I'd spent the longest time creating a wrestler, right? Cause you pick each and every one of their moves, you assign stats and then your own you're building the physical, but then even the costume is a whole other thing, right. It's essentially a whole other avatar when you can wear full body suits. And, then yeah, you're designing stadiums, your entrance music, your video, your dances. That's crazy. Your taunts. That's wonderful. [16:55] Jason J: And, all that stuff is in game, which typically is stuff that, you know, you and I've dealt with more as an external game thing. Like the content creators in studio are actually doing an internal editor and whatever, but this is all in game. And now you have the public also contributing. So there's like a large community that is, contributing, created content that they're making on their own. And like putting up on a, on effectively a download store, the store doesn't actually require any money or anything. You can just download it, but it's like a shared space where people can share their characters and their I've seen like kind of crazy ones. [17:31] Jason J: Like people will build like, presidents or they'll build like Muppet characters or superheroes. And they'll kind of post them up there and people can download them and use them in their game. [17:40] John: That's the best man. Self-expression user generated content, right? Just gives your game. a whole other tale. You really don't have to build battle passes and season passes and updated content. When you give users these tools to kind of build the content for you. So it's super smart. [17:56] Jason J: Yeah, I've definitely watched a few streamers. as I was heading into this product, I was like, oh, well, what does that entail? And I watched a couple of people that they have full on YouTube channels, where they, for one, they stream like the story mode as they progress through it. But then they create their own story. they use the tools in the game to make, a progression for their character. And then they, as part of the kind of voiceover for their, YouTube stream, they'll tell the story, like what's going on. And what's the motivation here? Like what are the stakes? And it's really cool to see them do that. And I'm like, man, that's a pretty cool thing to have available for players. [18:30] Jason J: And there's surprisingly got larger numbers of these content creators that do this stuff with every game, they'll make, new versions of the game and they'll tell their own stories. And coming in and being able to kind of lead the effort to drive the future of those things is an exciting opportunity. [18:47] John: Yeah, it brings two questions to mind. One, it's always surprising to me how, as a corporation. That I'm sure build similar types of things, right? Like create a player and NBA two K is different from creative player in WWE two K whatever. And you would think that you guys would talk and share tech and like build each other up. But usually what happens is the tech is super different. It's super proprietary. Only works for the type of game you're building. [19:14] Jason J: Yeah. I mean, there needs to be an effort to allow for those types of things to happen. if you're going to do that, most of the time throughout my entire career, you've gotten these, in these scenarios where the engine that's being used is so unique for whatever game is being made. That, that flexibility isn't there. I've worked in the past with engines like frostbite and, with, the rockstar game engine and with, uh, lumberyard or CRI engine, [19:40] John: You're welcome. And [19:41] Jason J: Yup. [19:42] John: oh shit. [19:43] Jason J: And all of those engines are built not as generically as you would like. have a very kind of wheelhouse place where they are, [19:50] John: Like first person [19:51] Jason J: yeah, it's a first person shooter and they do it really well. or, you know, you'll see things like, Some ability to do some open world, but it's not to the level of rockstar, which rockstars engine was, it was built on OpenWorld, everything. And so games that are more level based, such as a, max Payne three [20:10] John: Yeah. [20:10] Jason J: are actually just streaming in everything as though it was a rockstar, open-world game. They just don't fade up the screen until everything is triggered as loaded. Whereas a, in GTA, you'll drop in and the immediate area around you is loaded. But then as you walk around the world, like more of the world is loaded and things like that. [20:29] John: That's the biggest thing with open world games and I guess what separates them, right? It's like, how good is your loading? How do you, what do we call it? Fragment your data or chunk of fight. And a lot of these engines came at it from the other side, right. They kind of came from these linear corridor based or level based experiences. And then for them to retrofit everything. Okay. Now we're going to basically our open world is just a bunch of levels that load together. [20:53] Jason J: Or a gigantic level. [20:55] John: Or a gigantic level. Yep. Like a persistent level with many levels in there where they get like, very clever with how they place their sight lines and buildings. Right. So you can't see beyond this mountain or something. So you could just unload that level. [21:11] Jason J: Yeah. And a lot of that came out of the groundwork. That was the doom games and the quake games, like all of that was built around kind of these corridors and whatever to hide the loading because as the famous quote goes, we are limited by the technology of our time. nowadays we have a lot more powerful technology and so we can be a little bit more open and it's okay. Now problem is with all technology, a content creator is going to fill that hole. Like if you give them a little bit more time, they're going to say, oh, well I can put more stuff in. [21:41] John: or you tell us, oh, don't worry. You don't have to clean up your mess. Right. It's all Right. else will do [21:46] Jason J: So efficiency sometimes falters in that, in those, uh, those cases. [21:51] John: You ever seen that shit where this, like you're shipping the game and there's a bunch of random stuff near the origin of the world. Just eating up memory. [21:58] Jason J: Oh yeah. I have debugged that a lot. So red dead. That was one of my things I was, I would go there and I would find all these things and then find out where they came from. Then talk to the environment artists and be like, Hey, there's a bunch of stuff here. whoa, what does it need it for? And sometimes it's useful to do that. So for example, if you're trying to spawn in something for a random event, you can preload all of the things that you want to draw. for an example, like red dead, you want to draw a wagon, that's broken, you want to draw a fire, fire pit, and you want to draw like some horses or whatever that are, you know, falling over. [22:34] Jason J: you can preload all that stuff and then kind of have it at the origin. So if it does draw like it's underneath the world, no one can see it, And then when you want to display it, you can just pop it over there and you don't get kind of this, problem of like, Hey, it's trying to draw in the same place that it's trying to spawn and all that kind of stuff. now is that the best option? Probably not. You shouldn't be drawing it if it's not ready yet. But you know, sometimes there are a lot of ways to get at something which makes it difficult to say like, okay, I'm going to lock down this one way for you to open this door. It's like, no, there's like 15 ways to get beyond that door. [23:07] John: as an engineer, as a lead engineer, what's the typical day today, like, How would you cut up the pie of time spent with designers time spent managing time, spent coding time spent with producers or artists? Yeah. What's your typical day? Like? [23:21] Jason J: So it all depends on the size of your team and kind of the urgency at which things need to get fixed. the engineering lead always wants to kind of be coding cause they're a coder first usually. typically you'll kind of do a lot more adminy stuff that helps free up your reports. So then they can do work. so you'll be the bug triage as bugs come in and you was say, okay, well, let me look at this and make sure that it is a bug, for us or for some other team. you also do things where you're looking at a larger spectrum of problem as opposed to a narrow focus. for an example, if something is having trouble loading in a game you might be looking at well, are there other places where this is not loading as well? [24:00] Jason J: Or is it unique to this scenario where we're trying to use it? or you're looking for kind of nuance things that aren't as functional as that you wish they were like, Hey, you know, you're supposed to be able to move this slider and then something changes on the character. Well, if I move that slider. Does it move very, very slowly. Does it move very, very quickly? And you're trying to kind of tease out some of these things that are like, well, it is functional, but it's not as friendly as it could be. and that day to day can be unique per kind of company you're at and kind of what your mission statement is for your team. for some companies, the lead engineer is essentially just the person that doles out the bugs, they get this influx and they're like saying, okay, well, you're gonna work on this. [24:45] Jason J: You're gonna work on that. And then depending on the seniority, uh, structure of their team, they might also be kind of a mentor, uh, to the, uh, younger group of developers. Uh, if it's a super senior team, then they may be kind of just like a coordinator where they're just kind of like, oh, well, you're going to work on this and kind of chunk it over the wall and be like, all right, he's got it. and then there's other companies where that lead is now kind of more abstracted from the day-to-day coat. there are some leads that don't get to code much at all, because they're going to meetings, they're talking with design or art, coordinating all of the desired, options. [25:23] Jason J: And then kind of like saying, okay, this is the priority list for us. This is what we need to finish first and second. and then there's a planning element as well, cause. If you're in a studio that does agile, there's two weeks sprints. And you're like, okay, after this, we're going to get this stuff done. And then you're like coordinating with each contributor to say like, Hey, what did you get done? The stuff that you didn't get done, can we move it to the next sprint? Or do we need to move that into a backlog and say like, Hey, you know, this actually was downgraded in priority. [25:50] John: It's funny. you mentioned agile. I've never been on a game team that does not do agile or claim that they do agile. [25:58] Jason J: it is a bit of a buzzwordy type thing. and then some of that depends on what your production leadership is. I know that production really has, at least for the studios that I've progressed through. They've become more and more, friendly to the agile mindset. But I don't know if you know this, but you and I kind of went through the game industry as agile was discovered and implemented. [26:19] John: that's true. [26:20] Jason J: when I first started there, wasn't kind of this agile thing. It was like, Hey, [26:25] John: like, this thing has to be done before this thing could be done before that [26:29] Jason J: yeah. And there, there definitely was like, Hey, we have milestones. And those milestones had like, these are the things that we need to get done, but there wasn't that like, okay, this regimented like, okay, these are the things that we're specifically focusing on and kind of the stand-ups and all that kind of stuff that wasn't as. when I first started at all and as you know, at rockstar, we never did that. I never did any of that. It was like, okay, you have your bug list and you work through your bug list. My role here at rockstar, I definitely had a lot of people that were, day-to-day kind of coming up to me asking for help. And so I ended up, you know, not really using the bug list as much because there would be the walkup things. [27:09] Jason J: And so I had two lists, I had the walkup list and then I had the bug list. eventually I got to a cadence where I would kind of do what you do at a, uh, butcher shop. I would give people numbers [27:20] John: take a ticket. [27:21] Jason J: yeah, take a ticket kind of thing. And some of that is also you're triaging it. Like you say, like, Hey, you know, what's your problem. And how urgent is it? Like, Hey, I can not work or whatever. And then I would kind of say like, okay, well, this is my list of things. And you're going to fit in right here. And I would give them a number and say like, okay, this is where you are. Uh, and I had, at some point, uh, some of the content creators would come up to me and say like, Hey, What number would I be? And then, you know, I was, I would give him a number like, Hey, you know, I got six things ahead of you or something like that. And they say, okay. [27:52] Jason J: And if it wasn't like, Hey, I cannot work. Then they would either come back. Or they would say like, Hey, you know what, I'll write it in an email or I'll make a bug for it or whatever it is. And that helped mitigate a lot of the juggling. but at the same time, like there is kind of those things that immediately jumped to the top of the list where that, you know, supersede all of that stuff. And then someone comes over and like, Hey, I was the number one item. And you know, where's my fix. And you're like, well, this thing over here is on fire. So, uh, you know, you have to wait [28:20] John: Rockstar was an amazing place, especially when we came in, because for me, I had probably one year of experience under my belt before I got to rockstar, I had shipped one game and so getting to rockstar, seeing the power of the tools, I really felt like I had a lot of autonomy, there was never, ever any shortage of work. Right. You said, right. Bug lists, just keep coming. But we were essentially up, it was up to you how you wanted to tackle that load. Right. And to them, it was, Hey, as long as things are getting done, they're happy. They will be very in your face, the second something wasn't done that they needed done. Right. And it, it might not even be your fault. [28:59] John: It might've just came right then and there like five minutes before you didn't see your email and they're in your face. Like, yo, where's this, I need it yesterday. Right. after going through that experience, I became super good at balancing like a hundred different things at once. Right. And spinning multiple plates. [29:16] Jason J: I definitely understand where you're coming from on that. there were a lot of times where there was the negotiation. I have definitely had people come up and say, Hey, where's my thing. And I'm like, well, I'm working on this right now. And they're like, why are you working on that? Well, because X either, they'll say, oh, okay. Or whatever. there had been times that were kind of surprised things, as well as like, Hey, this is coming tonight. So we got to have it. And you know, there is a element of, dependence that, you know, you kind of continually going through and checking off the list triggers and people will say, oh, well, obviously he's going to fix it now because he's here. [29:47] Jason J: And while a short term game is not a longterm benefit. that's, that's something that I'm sure both of us experienced, with some of the kind of deluge of issues. I've experienced it at other studios as well, where it's just like, they just keep giving you stuff and you know, it's like, oh, well, yeah, I can stay or I can do this. And it just hasn't ended. The best when you allow that to happen for too long [30:11] John: And now that you're a lead, curious how you're applying your experience to the way your team operates, right? Like how many reports do you have? How do you manage that? [30:20] Jason J: right now I'm actively building a team. So I have a very small number of reports, but I will be adding more. And when you add those people, you are supporting them in a way to where, when you ask them to go do something that is a little out of the ordinary, it's not a problem. [30:41] John: Okay. [30:42] Jason J: So there, there is a mindset that comes in there for leaders. you want to be able to ask someone to join you in the foxhole, but you can't ask them to do it every day. if you do that every day, then they're just going to get run down with like, well, you know, everything is just blowing up all over the place. There's no real kind of consistency here. There isn't really a plan and it can be very frustrating for people. the thing that leaders should do, and I'm trying to do is make it to where, when I asked for something out of the ordinary, it isn't the ordinary, I'm asking you to do something, stay late for this, or, Hey, can you really focus on this problem? [31:17] Jason J: Because. It's something that is going to get us the benefit, that we need, but it's not an everyday thing. I am balancing that request for your time over the time to fix something. [31:30] John: that sounds ideal. I'm curious where you learned that [31:33] Jason J: this is a personal learning thing actually. cause most of the companies I've ever worked at, they just keep giving you more and as I got older and you know, you add a family and children, like there are moments that actually strike you and you're like, Hey, you know what? I really need to focus and do something different here. a anonymous anecdote was I was working at a company and we were working a lot of hours and one of the producer, people was hanging out with me and he was working a lot hours too. one morning I came in and we were kind of just doing the morning banter thing and he relayed this story that I was like, oh, well that, that actually like struck me as a person. [32:14] John: Is this Ricky or Kockler? [32:16] Jason J: I said, anonymous. [32:18] John: I just want to know who it is so I can give them their flowers. [32:21] Jason J: Uh, it was concolor. [32:22] John: Shout out to Dave. I got to get him on the [32:25] Jason J: Yeah, you do. He would be a very interesting person to, to deal with. he's one of the better, one of the best executive producers I've ever worked with. And I would love to work with him again. [32:36] John: Did you guys overlap at blizzard? [32:39] Jason J: he never worked at blizzard. He worked at Activision, he was on the call of duty [32:43] John: Oh, okay. I bet I knew it was under that umbrella. [32:46] Jason J: he did show up a couple times at the studio so as Battlenet we were hosting call of duty. And so he showed up a couple of times. So I had lunch with him, like once or twice. Yeah. But what he said was, he went home and we go home really late at night, like two, 3:00 AM easy. And he had gone home and he found his son splayed out on the countertop, just passed out and he woke his son up and he said, Hey, you know, why didn't you go to bed, blah, blah, blah. You know? And he was like, I was waiting for you. I didn't have a child at that point, but I was like, man, I don't want to do that to my kid. Like, I don't want to have them like staying up super late, kind of having these, break your heart moments where they're like, I just wanted to see you, but you've been gone so much. [33:31] Jason J: that was one moment where I was just, was like struck by that. And I was like, okay, I need to be aware of what I'm being asked to do. And I need to be more aware of the limits that I would like to impose. as a lead now, I definitely would be more cognizant of that. a lot of leads will kind of take the perspective of, Hey, if I can do it, you can do it. And that isn't true for everyone. Elon Musk is very famous for kind of sleeping in his office and like always working and all that kind of stuff, but he has the ability to do it and not necessarily have it affect his general outlook on life. and, and that's something that not everyone can do. [34:13] John: I'm with you, bro. I'm a believer in lead by example, but that has evolved today, it's not about showing your team that this is how work needs to be done. Follow my example. much more that two way communication for me to understand how do I get the best work out of you and then enable that and set up mechanisms that make that a possibility day in day out versus, do what I do. [34:40] Jason J: Yeah. And, you know, there are a lot of different personalities that we've dealt with in our careers. There are those people that just, they can't turn it off and they're just constantly working and, you know, that's what they love and they're not happy unless they're doing that. And then there's those that like, come in, I punched my time clock and at five o'clock or six o'clock I walk out and I'm done. [35:00] John: but it's a tight shift of solid work. You know what I'm saying? [35:03] Jason J: Yeah. And now there have been studies that kind of give you perspective on like, you know, when the work day starts to degrade into like you're actually causing more problems than you, are fixing. there are multiple studies that showed that that was a number around 10 hours. Like if you work more than 10 hours on average, statistically speaking, you are causing more problems. Intrude the product then if you say, okay, I'm gonna cut it off at this time and come back at it fresh after sleeping and having a moment. [35:34] John: Facts. yeah. 10 hours straight, for sure. I want to go back there's a lot that I don't know about you, Jay, where is home for you? Where did you come in? How did you even get into games? [35:46] Jason J: I am from a very, very small town in, Texas. the town is called Weimer. If you've heard of it. one of the 50 people in the world that has, [35:54] John: How big is it? [35:55] Jason J: the town is, was struggling to be at 2000 people. When I lived there, it dipped down to about 1800 now. we have two full on stoplights that blink, you know, yellow, green, red, and then we have one Blinky light that blinks yellow or red, depending on the direction you're coming from. we are on interstate 10, which has been a lifeline for the town, because we have truckers that stop and things like that. Uh, it's halfway between Houston and San Antonio on interstate 10, [36:22] John: So people generally migrate to those cities. [36:25] Jason J: Oh, yeah. Houston has kind of grown out a long way. San Antonio has more grown towards Austin. Uh, the corridor, which you're experiencing Austin, you know what is. [36:35] John: Yup. Yup. [36:35] Jason J: that's kind of where we are right in the middle of nowhere. And, to be honest, there's not a lot of access to some of the things that you would get in a city. my parents were always encouraging me to learn things and my, grandparents were always telling me to learn things. but I didn't actually start programming until I went to college. It was late eighties, early nineties. I started to show interest in things like computers. Um, my dad and my mom were both kind of encouraging technology. Like they saw the value in it. And so there was like, okay, well we're going to go get a family computer. And of course I was like, well, what games can I get? [37:10] Jason J: we had a, a 3 86 the games on it were games that you had to kind of convert into dos modes. So you couldn't run windows 3.1, you had to run dos and then you had to flip some of the drivers on the audio device. So then it would play through the sound blaster audio card. [37:28] John: Creative sound blaster. [37:30] Jason J: Oh yeah. that's something that my mom would. And I didn't really care about it. Cause I was like, give me the games. Like that level of kind of fiddling with the machine, I was not as interested in. [37:40] John: that's pretty awesome. That both of your parents, your mother and your father were tech savvy back in those days when like computers were not everywhere. my mom and dad shot, I was there. It, you know what I'm saying? [37:51] Jason J: yeah. [37:51] John: know how to operate those things. [37:52] Jason J: Yeah. I mean, a little bit more backstory on that is my, dad actually has a degree in electrical engineering [37:57] John: Oh, there you go. [37:58] Jason J: my mom has a degree in chemistry. and she became a school teacher, for all my sciences, I had her so shout out to miss J so he always tinkered with stuff. Like at one point he was holding down five jobs when I was a kid, like really young, like I wasn't able to walk or anything, but one of the jobs was like he was working at a television repair shop and he was fixing televisions and fixing, anything that had like, a processor board in it, that type of stuff. we had that stuff around the house, like just, you know, old processor, boards, vacuums and stuff like that. So it wasn't something that was hidden from me in terms of like, dealing with kind of technology, but it was something to where it was. [38:37] Jason J: I wanted to do the thing with it, as opposed to like, mess with the internals. Like I wanted to play games or I wanted to watch a show if it was a VHS player or something like that. And I didn't really care about how it worked. I just wanted it to work. [38:49] John: So I can start to see games on the 3 86. It was already kinda set up for you, so you didn't have to figure out the instructions or how to set it all up. You said that you didn't get into programming, a tape, got to college. [39:02] Jason J: Through high school, I started to get more interested in the, more it hardware side of things. And our school got a grant from the government, uh, to build out a computer lab. So it was like, well, would you like this? build the computers. And I was like, okay. And I would set them up and get them working. And I started to feel that inkling of like liking the internals of how stuff worked together. And I would like make Frankenstein machines, like I would like open it up, add extra Ram, add more hard drives, you know, just random stuff just to see what it would do. now I know there's a lot more into just like, instead of just plug and play, there's like more things to do, but at the time it was like, okay, well what can I do? [39:39] Jason J: And get it to work. And like shell shove more Ram in shoving, other floppy drive in and shove, like more hard drive space and just to see what it would do, It was something that actually became very easy for me to do. I could visualize it in my head, how the pieces fit together and it was easy for me to understand it. so when I was thinking of like, what am I doing in college? It was like, oh, well, I like this, you know, it's simple for me to understand, like, why don't I do computers? I had never been really taught a programming language. so I, senior year of high school in Texas, they have a thing it's an academic competition series. So Effectively it's like a sports competition, but for, academics. [40:18] Jason J: And they instituted a programming one, like my senior year. And, you know, because I had been messing with all the computers or whatever, you know, people were like, oh, well, you should do the programming thing. and me and my best friend, we're like, yeah, sure. We'll do it. And so they're like, okay, well the language for this is C plus plus. So here's a book, go learn it. so me and my friend were messing around with stuff, but we didn't know what we were doing. Like, we didn't really read the book very closely. We were just fooling around with computers and making them like, count for hours on it. They like, you know, incrementing in an integer or something over and over again. [40:54] John: if you were anything like me in high school, the only real books I read were comic books, man. So you can give me a book that says, Hey, here's the meaning of life. And I'm just like, I'm going to skim through it. Try to see if I can get anything I need. And then just it aside. [41:07] Jason J: I will admit, I did not like school at all. that is kind of the dichotomy of my existence. I love learning. I love being taught new things. And when I ask someone about themselves or their history, I am genuinely interested in learning about you, your experience and your history. [41:23] John: That's true. I'll [41:25] Jason J: But I hated school so much. I did well enough. Like I wasn't like a, you know, a dropout kind of guy, but wasn't the star student, It just never really interested me as much as, you know, my school teacher mother would like, [41:39] John: what happened with the competition? [41:40] Jason J: so we sat in the room and I was doing C plus plus, and like, it felt easy to understand, like I could understand what was going on, like syntax of language, how you construct things. It became kind of the same kind of feeling as putting together those Frankenstein computers. He was like, oh, I take a little bit of this here and put a little bit of that there. And I could understand it. now I didn't realize that until like right before I took the test. So I didn't do well on the test, but after I was done, I was like, yeah, you know, this is kind of interesting. and maybe I'd like to learn more about it. I then was like looking at kind of universities and what do they have? [42:15] Jason J: And things like that. And at the time there weren't a whole lot of programs that were just like, Hey, you know, you're doing computer programming the whole time. [42:22] John: Well, computer science is a popular curriculum at most engineering heavy schools. [42:28] Jason J: it is, but it's also very difficult to get into and this actually was a Texas a and M university. [42:34] John: oh yeah. [42:35] Jason J: I tried to get in and engineering at Texas a and M university is very highly lauded. So it was very difficult to get into the computer science program. what I got into was the computer engineering program, which is much more of the hardware kind of interactions of things. [42:50] John: It was the same thing for me at my state school in New York. I want computer engineering because I don't know those were the buzz words I would hear all the time. and so I'm sure that worked in my favor because it was a lot less popular compared to comp sigh. [43:03] Jason J: I started there and my whole like problem with school kicked in again, and I wasn't able to get to the things I was interested in fast enough, [43:12] John: Yeah. They're going to give you all kinds of low level foundational stuff. [43:15] Jason J: it wasn't even like I was doing computer stuff. It was like, okay, you're doing all your Englishes. You're doing all your kind of maths [43:22] John: Yeah. Discrete math. [43:23] Jason J: you're doing your, other things that aren't kind of working on these computer things that you're like, Hey, that's what my degree is. So why am I not working on that? [43:30] John: And they don't look anything like games, [43:32] Jason J: Yeah, they don't at all. And I took a C plus plus class my first semester, or maybe it was my second semester. I did well in there. one of the things that really kind of triggered me as like, Hey, maybe I should do programming. instead of computer engineering was, our class is teacher was stuck in India due to some sort of visa problem. And so for the first, like half of the semester, we were getting taught by TAs. [43:58] John: which I'm sure we're not good teachers. [44:00] Jason J: they were not, but they were, you know, moving at a, pace to where I knew what was going on. Like all of the homework they gave you, like, I could do like real fast, like I was able to do it. And it just made sense. it was interesting, cause the teacher came back after a while or they got their visa thing figured out and he just came in and just started teaching the curriculum as though we were caught up to where he would be. [44:23] John: Ooh, [44:24] Jason J: he came in and the first thing he started doing was pointers. And we had not been exposed to pointers yet. [44:29] John: God, [44:30] Jason J: and he was just like rattling off stuff and like, Hey, what'd you do this? And you do that. And eventually one guy in the classic raised his hand. It's like, what are you talking about? And yeah, and me sitting in the class. I was following him, like I understood what he was doing and I don't know why it triggered in my brain because I had just been doing random, like programming on my own. And I knew that he was going a lot faster than the TA's, but I was like, oh, well, this kinda makes sense. I understand what you're kind of doing, but everyone else was kind of lost [44:58] John: a lot of people struggle with pointers and memory and D referencing, right? Like, Hey, is this a copy of that thing? Or am I looking at the actual value of the thing and why is it not changing? [45:08] Jason J: yeah. That is something that's definitely part of the programming test too. You know, it's like, you go with like, well, what is a pointer and what do you, how do you use it? And, you know, those types of things [45:17] John: those syntax tests. kind of jerks, right? Like they throwing things at you that a compiler would catch right away that you wouldn't even have to think twice about, how they're all taught. Right? Like they try to make sure that, you know, this [45:30] Jason J: that's one of the things that I think is maybe a little, too heavily weighted nowadays, because we have tools that tell you Hey, don't do this. Or, you know, this, this is not going to compile. but that was kind of the programming tests that I had were those kinds of oriented things where you would, fix up something on paper and then. make sure that you have the syntax right on paper. but anyway, given that I would did fairly well in that class, I got, I think, a B or something in that class. So, that was something that was like, man, I did really well in there, even though it was like this mad rush to the end, and it really kind of drew my interest and I was like, oh, well maybe I should have done computer science. [46:07] Jason J: then I was like, okay, well, what if I transfer? So I went and talked to the, you know, the advisor and whatever. And they were like, well, you can't transfer to that degree because your other classes aren't high enough and GPA or whatever it is. So you can't actually move over there because they require a certain level. I ended up leaving Texas a and M like I finished my first year. And then after that, I was like, yeah, I'm not interested in this. I'm done. I remember the moment my dad sitting out with me on the porch drinking a Dr. Pepper and he goes, so what are you going to do? And I had spent some time and I was like looking at other programs and it's like, oh, what is this school that doesn't offer a four year degree? [46:43] Jason J: They offer a two year associate, but it's very focused on doing the work. Like it's more a trade school type of setup. and that school was, uh, Texas state technical college, uh, which had a business oriented programming class as well as a, computer hardware program. And, you know, the, the ego gets hurt when you don't really get to do the thing that you wanted to do. [47:06] John: Absolutely. [47:07] Jason J: So I was like, well, I can do everything. And so I went in and signed up for both degrees and tried to do both degrees at the same. that was difficult. but I also wanted to get out of there as fast as possible. So every semester, including the summer semester, I loaded up my docket with every hour that I could get. [47:26] John: So you double majored. [47:28] Jason J: I did double major, and at one point, I got a job as a pizza delivery driver. And at the same time I was taking five different programming languages, because they taught Vinny different ones as part of this program. And that was not fun. I had tests where I actually would get the right answer, but I would switch the language and syntax. [47:48] John: a coding language is still another language, right? you're training your brain to think in this world or syntax. And it's going to get confused if you're learning the things all at the same time. [47:57] Jason J: it was tough. my teacher was a really good teacher. shout out to Rodney cortico. he was a really good teacher. He really was excited about doing programming and it helped inspire me to do it even more he was also cognizant enough to recognize the strain that I had put myself under, saw that I was coming to class kind of extra tired. Uh, I was doing all the work, so my, my academics weren't suffering, but I was tired and I wasn't as energetic and things like that. And then one time I delivered pizza to him and he answered the door and he was like, oh, this is why you having showing up the class kind of tired and things like that. Cause you're, you're doing this job as well on top of, you know, doing the crazy workload that you're doing. [48:40] Jason J: And you know, that, that was a moment that was very poignant in that it showed that someone cared and I wasn't just a number for the school. Like they were like, Hey, your wellbeing is, something that we care about. And so it kind of stuck with me and I became friendly with him, as well as another teacher named Susie walk-ins, who shout out to her as well, who, actually got me to switch into the gaming world. I was about done with my degree, my two degrees at Texas state technical college. And she, had worked at a company that did GBA games. [49:14] John: Vance. [49:15] Jason J: I was like, you made games. How did you do that? How did you get into that? And it was like, I barraged her with a bunch of questions and, you know, gave me the, you know, well, you know, this is what I kind of fell into this, or this is what I did. And so I ended up finding out that there were colleges that actually specialized in teaching games. and at the time there were two, there was full sale and there was, up in Seattle, full sell being in Orlando, Florida area. so I was like, oh, well, that's really cool. I want to do games. all of my projects in school were essentially game oriented. Like I did a whole like, English project where I was like pitching a merged kind of game that was like, two games that I really liked playing and merged them into one. [49:57] Jason J: And I was like, pitching it as part of a presentation that I had to do in that English class. It was like, uh, I don't know, it's public speaking type thing or something. I don't know. [50:04] John: was the game? [50:05] Jason J: it was a game called, uh, championship manager, which is now moved to football manager as a name and FIFA. [50:13] John: Oh, so it's like manager mode, like the team [50:16] Jason J: It is, but it's much, much deeper. Like those of you out in the audience that have played championship manager or football manager know that it is quite an elaborate game. and FIFA had a manager mode but the. For this game is way, way beyond FIFA. Like they have leagues in there from all over the world. They have multiple lower tiers and all of the, all of the leagues and you simulate, like all of the games you simulate, you can set up tactics in the game and you you're essentially a manager, but you can buy and sell players. And there's a lot of like media interaction and there's a lot of stuff in that game. I still play that game. I still play the newer versions of that game. [50:58] Jason J: It's, one of those things where it's kind of a turn-based game. So it makes it to where it's a little easier for you to click it and then walk away and do something else and come back. it's a game that just draws me in because I building my own story in my mind. [51:10] John: So Susie Watkins is the reason you found out about full sail. [51:14] Jason J: Yes. and, during my final project and I had been inspired by her, I was like, you know what, I'm gonna have a degree in computer science. Let me just try and get to a game company. And at the time, there was the age of empire studio, that was in, Dallas area. that studio no longer is there. I don't believe, but they did age of empires and age of empires was a game that I played a lot. And so it was like, oh, well, I'd love to work with them. Uh it's ensemble studios, I think. [51:41] John: Ensemble. There we go. [51:42] Jason J: Yeah. [51:43] John: I was racking my brain. I was like, [51:45] Jason J: Yeah. [51:45] John: the hell is it? [51:46] Jason J: I was like, oh, well, I can obviously get a job over there. I'm a computer scientist person. I can program a computer. and so I emailed them and was like, Hey, or I'm about to graduate. And I'd like to know, like what opportunities you all y'all have available, you know, what kind of things can I do, what kind of things are you looking for in a candidate? And they basically sent me back, Hey, we're looking for, do you have 3d experience with, direct X? And I was like, well, no, you know, I've done business software. Like there's no direct X and business software. I was a little disheartened by that because I was a quality, obviously I can, I can figure it out. [52:24] Jason J: I mean, problem solving and whatever, but that seemed to be at the time, a lot of the gold standard was, do you have experience with direct X, every position, gameplay, audio, whatever it was like, do you have experience with direct X, uh, or open GL? that led me to try and do it myself. I was like, oh, I'll buy a book and I'll try and figure out direct X on my own. And as I was doing it, I was like, you know, this is all in my free time. I'm working a job as well as doing this. I really would like to have a more focused. Kind of time for this. And so because of Susie, I had kind of looked around as well at those schools and looked at Japan and looked at full sail. [53:05] Jason J: And oddly enough, the thing that led me towards full sail was the shorter length that you had to do. So full sail was offering a two year degree, that you could do. And I think 15 months is what they call it. [53:18] John: the associate's 15. The, bachelor's like 21. [53:22] Jason J: well, so they didn't even have bachelor back then. [53:24] John: you were, [53:25] Jason J: Oh yeah. Um, wailed, and then, I looked at digit pan and it was a four year school [53:30] John: an expensive [53:31] Jason J: and expensive. And I was like, man, this didn't work out for me before, when I went to Texas a and M like, I don't know if I want to do it again. Plus I'm now moving to the Northeast, uh, where, you know, a much farther away from my family. And so if it fails, like it's going to be really tough. [53:47] John: yeah. like Orlando, the flight is like an hour and change. [53:51] Jason J: Well, I drove [53:52] John: Well, it's drivable, [53:53] Jason J: It is driving. [53:54] John: Texas is, Seattle's a tough drive. [53:57] Jason J: that's a big, of a drive. There's a mountain range in the way or something, my girlfriend at the time went with me to go visit the school. We flew out and visited the school and we wandered around. And as you know, full sail, they have a lot of pomp and circumstance that they do. there, there weren't as many buildings as when you were there [54:13] John: Did you just have the one side? [54:14] Jason J: it was one main building. And then they had just taken over part of that, strip mall where the Wendy's was, [54:21] John: Yes. [54:22] Jason J: just taken over just part of that. [54:24] John: my God. That Wendy's bro. [54:26] Jason J: oh yeah, we hit up that Wendy's all the time, [54:29] John: nuggets. [54:30] Jason J: yeah, the school, I did the tour and they were showing me around and at the time, there was this mystique of like, Hey, you know, one of the creators of D and D is one of the teachers here. And so, yeah, Dave Arneson was a teacher there and they were like really hyping it up. And I have to admit, I wasn't really that dandy cause I didn't have a group of friends to play with. [54:52] John: me neither meaning they would, they would tell him about this guy. And I was just like, Yeah. I mean, show me the games, [54:59] Jason J: there was people that were like, I have to go to this school because of him [55:02] John: Yeah. It's a great recruiting tool. [55:04] Jason J: they were definitely hyping that up and they had a lot of the very nice looking classrooms and things like that. And they, you know, gave you a laptop to work on and all this stuff. [55:13] John: cutting edge and modern, that was the biggest difference I noticed when I went to visit it. [55:16] Jason J: you know, after we were done, my girlfriend at the time looked at me and said, if you don't come here, you're crazy. [55:21] John: Wow. She told you that. [55:23] Jason J: yeah, I mean, I was on the fence because it was a thing where, you know, I never really thought I would leave taxes to go somewhere, like to get a job or whatever. I would figure that I would go to Austin or Houston or San Antonio. You know, that's normally kind of the extent of the, the bubble of life in, in my area is usually you kind of go to those cities. and so I was like, oh, well, you know, do you think? And she's like, well, you have to come here. [55:48] John: What was it that gave that impression? [55:50] Jason J: there were two things. One was that, I had been talking to her before about like, I want to make games, but then as we were there in the school, they were hitting all the right notes, saying like we're focused on making games. we want people to make games and this class, we teach you programming. And this class, we teach you how to do the graphic stuff. And this class, we teach you about how to set up a story and, we help you with your resumes and all this kind of stuff that was like checking all the boxes of like, man, that's going to get me that job at ensemble easily, [56:20] John: Yeah, dude, [56:22] Jason J: you know [56:22] John: they told you you needed to know? full sail is going to teach you. [56:25] Jason J: Right. And so it was like, okay, well make sense. [56:29] John: how many degrees on the belt. [56:31] Jason J: I had only one because I stopped two credits short of getting my second I burned myself out and that was the first time I burned myself out. [56:40] John: A thought you thought you would've learned. [56:43] Jason J: yeah, I would've, I thought so, you know, it's, it's one of those things where I look back and I go, well, you know, maybe I should have stayed and done it, but I think the decisions that I've done in my life had led me to where I am. And so I can't argue with the outcome. [56:57] John: absolutely, bro. I want to unpack burning out. How do you know you've burnt out? And then what results from that? [57:05] Jason J: So for me, it was a lack of motivation, [57:08] John: You just drained? [57:10] Jason J: basically I would co in school do my programming classes, then go home and program. [57:17] John: Oh yeah. [57:19] Jason J: it'll then go, go to work and, you know, all that kind of stuff, but I would do it all the time and I just couldn't stop. Like, it was just, I was interested in it and whatever I was doing, I was like either fiddling with the thing that they had in class or trying to make up my own things. Like I started like looking at the games that I liked and trying to replicate systems in there to say like, Hey, you know, uh, tic-tac-toe for example, like I want to make tic-tac-toe or I want to make solitaire. And so I'd kind of try and do those types of things as I was learning. And then, you know, it just became a thing where I was doing it all the time. [57:55] Jason J: And eventually it just was too heavy, doing the homework for five different programming languages, doing the lab work for five different programming languages, doing the home stuff that I was doing, plus working and then doing any kind of gaming at all And trying to hold down a relationship with a girlfriend at the time, [58:13] John: something had to give [58:15] Jason J: had to give and I lost kind of my motivation to do that extra stuff. Like I would do my classwork, cause that was kind of my job. Like my job was to do school but all of the extra stuff, the things that I was the most passionate about and the things that were like, I want to do this for a job. I just didn't want to do it in. [58:32] John: that's it, man. As you talking about this thing, it's hitting home. I empathize with you 100%, right? Like the thing that excites you and motivates you, it's a complete 180, like, fuck this. It [58:43] Jason J: Yeah. [58:43] John: the same effect and well, cause you overdid it. [58:45] Jason J: Yeah. that's something that I didn't learn the lesson from the first time, but I definitely learned this lesson from the second time. [58:54] John: There. There are those of us who are much more thick scold, and it takes a few times for the message and lesson to hit home. And that message would be more than happy to keep punching you in the face until it finally sinks in. What happened on the second time? [59:07] Jason J: Well, the second time I was employed to do a job [59:10] John: Oh, that is very different. [59:12] Jason J: I had no motivation to do that job. And so now this is affecting your livelihood. I never got to a point where my performance was degrading to the point where kind of management stepped in and was like, Hey, what's wrong. my own motivation was just not there. Like I wasn't as passionate and I wasn't as interested in doing all of the things that I had done leading into that, [59:34] John: will you hourly [59:35] Jason J: they're in a second time. Yeah. Salary plus, Overtime. So. [59:39] John: Damn Jay you're opening up some wounds, right? [59:42] Jason J: Yeah, it can hurt. but the thing is, is you need to be honest about that hurt. that's something that I've never really been good at. I've always been very private. I've always been very guarded. I've always kind of had that, for lack of a better analogy. Like the kid that gets picked on at the high school, in the movie, like I was always the guy that got shoved into a locker. Did I ever get shoved in a locker? No, but you feel like that, like you feel like you're not part of the crowd, you're not cool enough. You're not part of this kind of culture that is like revered, like the party culture or whatever. So, being honest about, Hey, I don't feel okay or I, don't have this motivation anymore is scary. [1:00:23] Jason J: And so admitting it to other other people is really hard. there's a lot of times where you deal with things on your own that you don't really show with other people and it makes it to where sometimes people that aren't necessarily as engaged with you don't see that in you. And it becomes a, point where you get more isolated because they're like, oh, I want to hang out with that person. They're just a, they're a Debbie downer all the time. But in reality, like you're really struggling with stuff and you're just not talking about. [1:00:50] John: yeah, man, I grew up, you know, I had my basic needs taken care of, but definitely felt poor financially. And so being in a situation where it's like, here's more money to do more work to me, it was like, oh my gosh, I have no business complaining. Like I need this money here they are giving me more of it for my time. [1:01:12] Jason J: yeah, it's a bit of a drug. never without, like, you're, like, you're saying like I never did without, but when you're looking at your history, you're like, you know what, we weren't that well off. And my parents admitted to me more recently that we weren't that well off, but I never really felt it as a kid. Cause [1:01:30] John: Never felt that. [1:01:31] Jason J: either you don't know any better or the person that got whatever thing that you would like to have. You rationalized it as like, oh, well I can get that later. Or you know, my parents would save and get stuff. So there was like, oh, well I'll save up and get that. [1:01:44] John: Yeah. I had, my Nintendo had my game systems. [1:01:47] Jason J: have a Nintendo. I didn't have a lot of the game systems, but a friend of mine did [1:01:51] John: got a sweet PC [1:01:53] Jason J: well, sweet kind of it had a turbo button. So you knew it went fast. [1:01:58] John: overclock as sucker [1:02:00] Jason J: but it was a thing where, you know, I never knew the actual perspective of we were kind of in that financial realm. [1:02:07] John: and that's a great place to be, right. Like that [1:02:10] Jason J: Yeah. [1:02:10] John: of just like, Hey, this is my normal and life is good. [1:02:14] Jason J: Yeah. And there wasn't any kind of like, we're not going to eat if, or, you know, we're not gonna, we don't have power if, or we don't have clean water. If so. Yeah. And I was, I was very lucky to have that, but there definitely was a, Hey, everyone else had a lot more things than me. And, you know, I, I learned that a little later. get that perspective a little later. [1:02:38] John: I was watching something with Minecraft dude notch, [1:02:42] Jason J: Yeah. Notch. [1:02:42] John: he's on the other extreme, right? Like, here's enough money so that you never have to worry about money ever again. And he ended up in a situation where he felt alone, right? Like the money, put them in a space that not a lot of people could relate to. He's still his same self, you know, looking to make the same connection you used to make online and share his thoughts with people. And, but. They essentially canceled him and dismissed him. Like, Hey man, you have no place to feel sad or complain. You're a billionaire. How dare you? And that's crazy right. You know, he's still trying to make connections. Same way he did by building Minecraft. But, Hey man, that's, uh, another conversation that I can sum up by saying, always know your why, why is it that you do what you do? [1:03:22] John: And. First, you know, On the other end of that spectrum. but still to be like the money no longer motivated. You neither did the work, It was just over done. [1:03:33] Jason J: Yeah. And at the time when I was doing that, I had a girlfriend, a different girlfriend than the one that told me to go to full sail. But, I wanted to spend time with her. I wanted to see her and like my priorities shifted a little bit. Cause it wasn't just, oh, I'm going home to my kind of communal apartment with, you know, my roommates. It's like, no, I want to spend time with her. So that made you start addressing like, how long am I at work? Like how late am I staying? And you started missing out on things on occasion. Like, she would call me and be like, Hey, me and a few of the friends from the, her work are going to have dinner. Would you like to come? [1:04:07] Jason J: And I'm like, I can't or, Hey, we're going to go to St. Patty's day party. Can you come? And I'm like, I can't. And you know, it started to kind of be like, well, what am I doing here? Like, why am I here by myself, wishing to be with someone else? And so it, it changed perspective. and I was heading into a space where I did end up burning out again. like, it was difficult to get up and get in to work, but there was that motivation there of like, Hey, you know, you have to deliver because that affects your money. That affects your ability provide for yourself, like food on the table and rent. [1:04:42] John: you also had a pretty key role on the team [1:04:47] Jason J: So my role at rockstar was one of two tools, engineers that were supporting the local team of 300 and the remote kind of extra worldly team of 600 plus because we had north helping us and we had, uh, new England helping us. And we had, I think, uh, Toronto and I think QA or someone in, uh, New York was helping us as well. And so we had all these studios that needed to work with our systems and, you know, they've, they've now shifted, but at the time, uh, San Diego studio had its own version of the rockstar game engine, its own version of the, uh, tools to build content and to produce content. So of that stuff was kind of be supporting, being supported by myself and another engineer. [1:05:39] John: Yeah. I think the role modern day is referred to as like a build engineer. really? [1:05:43] Jason J: maybe, that was part of my role. at other companies, I have definitely been taken aback by the specializations and breakdowns of the role that I actually did at rockstar. [1:05:54] John: Which had like five different [1:05:55] Jason J: Yeah. So there was like the build engineer, there's the tools programmer, there's the, pipeline engineer, which is dealing with kind of the content. And then there's also a resource engineer which deals with kind of translating the created content into the stuff that gets shipped on disc. all of those were part of my job. And so when you go to other companies that are a little bit more split up and there's like, oh, well this guy just deals with the bills or this guy just deals with the tools. why did both of those jobs, like, you know, yeah, yeah. that is also kind of a luxury item that some studios don't have, like if the smaller studios you start wearing those multiple hats. [1:06:36] Jason J: so it, wasn't a thing that I was not used to. [1:06:38] John: what was some of the ways that you were able to kind of motivate yourself? What were some of those interactions with? Maybe some other coworkers that kind of like reinvigorated you, riding kept you going. [1:06:49] Jason J: as many Marines will say, it's the person next to you being in. Foxhole with you that motivates you to move forward. I was lucky enough, but also kind of had the problem of, there were people around me that were in the same kind of boat. there were several engineers that I worked with that were kind of there all the time and they, were familiar. They were, friendly to me, at the office. And, you know, there was one engineer that we had. It was like a, a joke where, okay, tonight you're going to stay. And he would go home early and then tomorrow he'll say, and then I'll go home early. And, you know, we had little kind of comradery banter around that those are the people that made me kind of be able to going and had the motivation. [1:07:29] Jason J: Cause I didn't want to let them know [1:07:31] John: That's what I was going to say. on that team, on that product, a big part was that band of brothers feeling right for better, for worse, there was a lot of us in the trenches. You could say definitely depending on each other, but also not wanting to let each other down, you know, and trying to all work towards making the best product you can make. [1:07:49] Jason J: a lot of companies are trying to integrate. They're trying to create that scenario. And there is a fine line there for leadership to walk because you want to create that comradery. Cause you get great communication or great collaboration out of like, Hey, we're have a shared goal. We're all working towards things and I trust you to work hard and you trust me to work hard, but there's also like just throwing more and more work at you and not letting you take a breath. some companies don't do it very well. Some companies do it a lot better. I don't think there is a company that does it perfect yet, but there is a onus on leadership to understand that and to progress towards making it as good as possible. [1:08:30] Jason J: And that's knowing the trade-offs like knowing, like when I asked you to come do this thing to stay late, like you will do it, but it's not because I'm telling you to is because you want to support the work that I'm doing because I'm supporting the work that you're doing. [1:08:44] John: I love it. J we come back around full circle to the lessons learned that you bring into your leadership style today many, many years later, right. Trying to create an environment that's conducive to that mythical work-life balance and games thing, and, leaving the industry better than when we got in. [1:09:02] Jason J: so my wife is a, uh, cardiac ICU nurse and they take a Hippocratic oath. And essentially what that boils down to is a simple phrase, do no harm. And so as an engineer, I take that as well. Like do no harm, like when I do something, make a change to something, it doesn't bring down the product. It makes it to where it is functional and running. And while it may not be the final thing that you want, like there may be bugs in it. It does not cause catastrophic failure. [1:09:31] John: Okay. So [1:09:32] Jason J: uh, [1:09:32] John: your self-imposed. Oh. As an engineer. [1:09:35] Jason J: I mean, I've definitely read other books where kind of people have alluded to kind of like having that professionalism around you. And that's something that is interesting a as a debate in the programming space, especially in games, because Terminology is more around, well, I'm a hacker or I'm a programmer or whatever, [1:09:53] John: it's move fast. Right? Move [1:09:55] Jason J: yeah. Or, I'm an engineer, but general, we should be striving to be professionals at our job. And that for many other jobs entails, you know, some of those certifications and things, but there's also kind of a mindset that comes with it. you know, when you're, when you're professional at your job and you're doing your job, when you say something is going to get done, you work to make it get done. If it doesn't get done, you say, Hey, it didn't get done. But here's why, when you are trying to communicate with someone about what they're looking for, you're respectful of what they're asking for. You're taking in kind of what their expectations are. [1:10:32] Jason J: And then you're honest with them about kind of results. Like there's, there's a lot of meme where the things where it's like the, the production side is saying, oh yeah, yeah, we got this done. And the engineer's sitting there going, like, it's going to take me four years to do this. And you know, so there is a professionalism that needs to come in. when you do that and as an engineer, I've tried to strive for that professionalism and not all engineers do that. it's more a personal thing. but it is something that allows me to build trust across different disciplines much faster, because I am able to say, I deliver this and it actually gets done, or I say, Hey, it didn't work out. [1:11:10] Jason J: Here's why, let me work with you to make it to where you can get some of what you want. Or I can tell you, this is the timeframe when this thing can be available. [1:11:19] John: That's the best thing in a teammate, right? Just constant communication, helping us figure out the expectations what's going to be delivered and specifically a value an engineer, right? Someone whose work kind of enables a portion. If not the entire game to come to fruition, [1:11:37] Jason J: yeah. And that is something that's a little strange as well is, a lot of the engineers that work on projects, don't, aren't kind of touted as the flashy, like bane plates. Like you'll have a lot of designers that either get kind of the flashiness or certain programmers that do a specific thing. if you say John Carmack in the gaming world for programming, like you really know, oh, that guy, like he is a name. [1:12:00] John: map a face. [1:12:01] Jason J: Yeah. And you know who he is, you know, kind of his contribution, but that isn't always the case. And there are a lot of engineers that are very talented, that can contribute to, you know, every product every day. [1:12:13] John: Yeah. [1:12:14] Jason J: And so something like a slack, for example, has engineers that cut that contribute to it. And those engineers aren't. Front and center like, oh, they're super awesome. It's like, no, the product is there. And internally they may be getting kind of kudos, but they don't kind of, you would say, run the red carpet and get, star lifestyle. [1:12:34] John: if I haven't told you, Jay, I value as an engineer and as a teammate for the word we went through on rockstar gate and red dead one out the door. [1:12:47] Jason J: I think final project, [1:12:49] John: Oh yeah. What'd you have three months. [1:12:51] Jason J: Yeah. So my team. were a little bit young and naive, I wanna say. [1:12:55] John: Hey, we we're all You probably bit off, more than you could chew. [1:12:59] Jason J: oh yeah. So we decided to make an RTS [1:13:03] John: Okay. Let's do a bull. [1:13:04] Jason J: and we decided to do it in direct X, which at the time was not part of the curriculum open GL was X was not. [1:13:12] John: Oh shit. Okay. Yeah, because when I went through, I got both, but if you're telling me you didn't even have it as a class, [1:13:19] Jason J: yeah, we didn't have it as a class. It was only open GL. [1:13:21] John: why was it the input? Was it the rendering? [1:13:24] Jason J: it just wasn't there. Like they didn't have it [1:13:26] John: No. No. what, I'm saying? Why did you want to make it in DX [1:13:29] Jason J: because of that email that I had gotten back from ensemble that was like, we want direct X experience. [1:13:36] John: leave this school without learning [1:13:37] Jason J: And when we looked at other jobs out there on the web, they always said direct X experience. So we're like, okay, well we're going to get this. Like the whole team saw that. And the whole team was like, yeah, we're going to get direct X experience. Now. I don't know if I convinced them. They just saw that. That was what the jobs were posting. [1:13:55] John: Even for the jobs they wanted, they [1:13:56] Jason J: Yeah. There, there, like, it was weird. Like the team came together and we immediately were kind of a team. Like there wasn't anyone that was like arguing over like, oh, should we do this? Or should we do that? It was just like, Nope, we're together. And we're working together and we're a team. And that was it. [1:14:11] John: the team? [1:14:12] Jason J: No, not for final project. we had our roles already. It was like, you know, you're going to do the AI and you're going to do that. I did the animation system and some other miscellaneous rendering things. And I dealt with all things, the content creators. So I was like stepping into that world right away. [1:14:33] John: Yeah. [1:14:34] Jason J: But we did an RTS. And one thing that I really like is the presentation day. So you come out and you present your product and you talk about what you did and you kind of have a script that you follow that kind of thing. And what was very cool about ours was, the teachers had seen what we were doing. Like we were making RTS and they knew that that was more complex than what we should have, but they saw all the progress we were making. Like in this game we had formations for the characters. We had multiple formations. We had a, dynamically created terrain that would draw a river in the terrain. So it would like use a algorithm to draw a river across the terrain. [1:15:14] Jason J: It would then populate that river with, bridges. So you could get across I and create choked. and we had audio and we had a full menu system and we had a full campaign. Like we had a campaign where you were taking over a little sections of the world. [1:15:28] John: What was your motivation? Was it like StarCraft? [1:15:31] Jason J: no, actually it was all the historical RTSs. So things like, age of empires. Uh, [1:15:37] John: Yeah. You, you really trying to go to ensemble? [1:15:39] Jason J: yeah, it felt like it, so we were doing this and the, TA staff was seeing us do it. And they were like really kind of hyping us up around the, around full sail. Like they were like mad, like other classes were being told about the, what we were doing. And so on presentation day, uh, one of the team members, his dad came and said like, Hey, I wanted to help you guys, you know, kind of be a team, blah, blah, blah. And he had made us shirts that had the logo of the game on it. And it was like, we had colored shirts with the logo of the game, on it, like button down shirts. And it was like, man, we're actually making a studio here. It felt like so cool. [1:16:15] Jason J: Uh, and then presentation came and that room was packed. Like every other class had adjourned early to come to our presentation. I think that even had a tour group that they brought in, it was like packed and S something like that. Well, so the room wasn't that big. It was. There were seating for maybe 70, 80, cause it wasn't a auditorium set up. it was just a large room and they had everyone standing. They had people sitting in front of the first row. It was definitely a fire hazard. [1:16:47] John: What was the name of your team? Was the name of the project. [1:16:50] Jason J: Uh, so our, our team was called TSB games. And the project that we did was called leash. [1:16:57] John: Okay. [1:16:59] Jason J: And I don't know if it ever made any sort of notoriety beyond this, this particular day, but we presented our thing and we had what I felt was a great presentation. Like we had a couple of things that didn't work out exactly, but it was a really cool project. And then we said, Hey, you know, thank you everybody or whatever. And then everyone clapped and it feels like, oh man, this is amazing. Uh, and then kind of a large section of the room left and then they did the other presentations. So it really, So we started out the gate and it was like, we were the headliner and then everybody kind of trickled out after that. And it was like, [1:17:43] John: You [1:17:43] Jason J: like [1:17:43] John: had to close. [1:17:44] Jason J: we did well. Uh, so that was definitely the coolest moment [1:17:49] John: Yeah. Geez, man. I didn't have that. I did. I closed my final presentation. And as you tell your story, I'm coming to find out you actually want to be the opener. I guess the [1:18:00] Jason J: Well, the opener that opens well, like I, we showed well, and that definitely helped kind of the experience I think they were, are showing the tour group that may have shown up was also kind of like, Hey, they're trying to come to the school. So they're trying to show you what final project is. Uh, you know, having other classes like, say like, no, we're going to go see what these guys had done was really kind of cool. [1:18:25] John: So you dropped the mic, you graduate out of full sail, and set sail literally into the game industry. How the hell did you break in? [1:18:33] Jason J: you know, I would like to think that, you know, oh, well I had these contexts already at ensemble and I was just like, call them up. And they're not, here's a job. [1:18:40] John: Yeah. did, you, did you hit them up as [1:18:42] Jason J: I did, I did apply, but they never got back to me. but one of the things I did, I did this exercise that. Coming out of school or when you are kind of in the middle of the school you can do, which is I took all the games that I really loved playing. luckily at that point, my game library had gotten bigger, but I started, collecting all of those games, flipping them over, looking at the studios that they came from, eliminating studios from places that I didn't want to go or didn't think I could go because I had several like European-based studios. And I was like, oh, well I can't go to Europe. so I flipped over the boxes, looked at those studios, then went to their websites and started kind of perusing the website, back then the recruiting mechanism wasn't as prevalent as it is now. [1:19:25] Jason J: now, everyone has a career section. Everyone has like a, resume, dump, email address or something like that. [1:19:31] John: Meaning when you go to a company website, like if you were to go to ea.com back in the day, they would probably just tell them about the games and how to buy them there. Wasn't like a come work for us. [1:19:40] Jason J: yeah, there wasn't as pronounced come work for us. Uh, so one of the companies advertised on their site and internship program. And so I got in through the internship program that is something that more studios have now, even when you're in this. I've definitely have been a mentor for an intern at one of my jobs where they were a sophomore in college. Like they hadn't even graduated yet. And it was interesting cause they had done multiple internships before. So they had things on their resume. Like they had done JBL, which is the jet propulsion laboratory from NASA and they had done an internship at Google and I was like, man, your resume is better than mine. [1:20:19] Jason J: Like I was like, dang. And they hadn't even graduated yet. so internships are a great way to kind of get your feet wet. Uh, some internships do focus on various pieces of game making, whether it's tools or graphics or, servers or gameplay. So you can also get a feel for like what you like doing without having to kind of do that. Well, I got this job and now I'm stuck here. Some universities help you I went to a, what was at the time considered kind of a community college level school. And they now have like, Hey, you know, we have an internship kind of person that's helping nail down internship opportunities for people. So if you have that available, look for it try and seek those out. [1:21:02] John: What are all the schools of engineering or what are the ones that you've typically gravitated towards? [1:21:08] Jason J: when you first hear about making games, it's like, oh, well the engineer does everything. but there are a lot of different aspects. So, depending on the game that you're doing, there's rendering, which deals with drawing stuff on the screen, there's the gameplay group, which deals with kind of making things happen on screen to whatever game you're making. but then you'll have things like networking, which deals with the multiplayer aspect of things. you have servers that deal with, if you are making a multiplayer game, it's like, Hey, how do you manage the game rules and all that? have a physics for dealing with physical like interactions, [1:21:43] John: destruction vehicles. [1:21:45] Jason J: vehicles, stuff like that you'll have focuses on, tools programming, which is, you know, dealing with kind of the, either the art tools, which focus on things like Maya or Houdini or MotionBuilder or 3d S max, or those types of tool sets that then you're kind of making plugins or making scripts to help the artists do whatever they're doing. [1:22:07] John: Yeah. You were essentially the hero of the developers, but players will never know what you [1:22:12] Jason J: yeah. And those are usually background kind of things like your you're standing up the team, but nobody knows that you're standing there. then there's other kind of programming avenues that are dealing with, even more fine grain stuff, such as particle systems or a specific aspect of graphics. So Like. there's, UI pieces, you deal with, things such as, Hey, we're doing water in our game. And so you deal specifically with water or you deal with character animation, [1:22:38] John: audio programmers are always a rare breed. [1:22:40] Jason J: or you do audio, which is odd because I really love music and I never really got into audio programming. I don't know why. [1:22:48] John: That's in such high demand everywhere. [1:22:50] Jason J: Yeah. [1:22:50] John: AI programming. [1:22:51] Jason J: AI programmers are out there, like, there's a large kind of collection of specializations nowadays that in the past really weren't as advertised as those specializations. It was more like. we need an engineer with all this stuff, and then they specialize based on our need. we need a graphics guy, so we'll put them on graphics, but we need a AI guy. So we'll put them on AI. Uh, nowadays there's definitely jobs that are specifically for like, Hey, we need a graphics guy that does this specific thing. Or we need an AI guy that does this specific thing. And you'll see it in job descriptions that say like, Hey, we need someone that deals with animation for humanoid interactions, which would be like, a grappling game, like a wrestling game or a fighting game, a UFC game, and there's a lot of human interaction at that, animation, is heavily used in those, those types of games. [1:23:40] Jason J: So you'll have a very specific role of doing that. My first job was a game company called big huge games. It was a small studio, but we did ship. a RTS. that was called rise of nations rise of legends. [1:23:54] John: I love that as the nations. [1:23:56] Jason J: Yeah. Rise of nations was one of the ones I first got my name on, I got my name on a next pack for rise of nations, but I didn't really work on it. I was working on rise of legends at that point. after that we shipped, a Xbox live game that was Katon, which was a port. [1:24:09] John: You worked on kits [1:24:10] Jason J: I did work on Katon. and for both games, I was essentially kind of a generalist. I did graphic stuff. I did, physics stuff. I did gameplay stuff. I did art support because we were a smaller studio. one of the things that I did for Katon was actually the skinning system. like, when you change from the, like I said, it was the maple scan to the 3d skin, like handling that was like my skinning stuff. was one of the aspects that I focused on. [1:24:35] John: I got to buy you a Shiner for those two alone man. [1:24:37] Jason J: yeah. [1:24:38] John: all the years we spent a rockstar playing basketball, going out to lunch, having drinks. And I did not know that I maybe I did [1:24:44] Jason J: I actually had Nicholas. Geek out on me on the dev floor. When I mentioned that, he he, was like, wait, you worked at big, huge games. Did you work on this game? I was like, yeah, I did that game. I was at, he was like, oh my God, that's so cool. And I was [1:24:57] John: dude. [1:24:58] Jason J: this is pretty cool. [1:24:59] John: Did you listen to Nick's episode? It's good. [1:25:02] Jason J: I did, listen to this episode. [1:25:03] John: Shout out to Nick [1:25:04] Jason J: Yeah. [1:25:04] John: episode. six, [1:25:06] Jason J: so after that I joined rockstar San Diego there, I ended up shipping red, dead redemption. I then shipped a max Payne three and helped ship. LA new R yeah, I was there very briefly. I don't even think I had any bugs assigned to me. I was just like over the shoulder, like helping a guy. [1:25:22] John: Sure [1:25:22] Jason J: I helped ship that. then I was the, first engineer assigned to what became red dead two. [1:25:28] John: damn. You had to stand it up. [1:25:30] Jason J: yeah, I stood it up and was supporting the design team at that point, as they were building out the world, I was also shifted over and working on GTA five for a year. I ended up leaving there and joining EA Redwood shores. and the, uh, studio that is now defunct visceral. I was disappointed to see them close that, but, you know, it's, it's one of those things. so while I was at visceral, I helped ship battlefield four, and then I was doing a lot of the setup for, battlefield hardline a good chunk of set up on that. [1:25:59] John: what would you say? Our Frostbites strength? [1:26:02] Jason J: it has a lot of things built already. it has like a, a build infrastructure that is generic enough to not be super specialized. it is fairly generic enough to be able to do stuff. there are the low level libraries. I mean, we're generic enough and flexible enough to where kind of, you could use those. But once you got into more of the specialization stuff, like, for example, in battlefield, you had the gunsmith thing where you could track a gun, uh, or you could craft a character. Like a lot of that stuff was very specialized for battlefield. And so when you did something like that, wasn't battlefield or slightly different than battlefield, you had to do a lot more modification. [1:26:41] Jason J: What you would have liked, but that is a problem with very mature, very focused engines in general. [1:26:47] John: where'd you go after EA? [1:26:48] Jason J: so after EA I ended up starting my own company for a little while. where I joined someone that I'd worked with at rockstar, my partner was wolfing, Ang ho. [1:26:57] John: Yeah, that guy wrote the rendering book. [1:27:00] Jason J: He wrote many rendering books, but he had a company and he and I had been kept keeping in touch. And we started a company where the focus was going to be around the tools, infrastructure, backend, like person is supporting the dev team, but not out front kind of roles I was thinking that, oh, well, this obviously is going to resonate with a lot of people because every studio I'd been at had the same problems with productivity and kind of iteration time. So as like, oh, well obviously we can come in and use our expertise and fix a lot of this stuff. we ended up getting, several contracts. This is where I got to work on the lumberyard engine. We did the particle editor, the rewrite and the re-skin and we added GPU particles to cry engine. [1:27:40] Jason J: So that's what our kind of contract was. [1:27:42] John: that's another shine. I gotta buy you. to, we're going to work up to a six. [1:27:45] Jason J: Oh, we're working on it. after that, there were some, issues that led me to need to go somewhere else. And so I ended up getting a job at blizzard where I worked at, the Battlenet side of blizzard for a little bit working on the desktop application. and then they started an internal, engine team and they were looking for people and I immediately threw my hat in and was lucky enough to be the first actual engineer hired for the team. Like they had two guys that were starting the team and I pestered them enough to where they were like, okay, well, we gotta bring this guy on. and I ended up doing a short stint there where I proved that I could do stuff. [1:28:24] Jason J: And so they hired me be on that team for the last three and a half, four years that I worked on that [1:28:30] John: This is their internal Blizz tech kind of thing. [1:28:33] Jason J: they started a brand new engine, basically to kind of unify a lot of the game team infrastructure as blizzard has a lot of game teams in it. Uh, if you look at their website, they're saying it's like, oh, there's the Diablo team. There's the Hearthstone team and all that. And they all use different tech stacks. And so from a corporate perspective, there was an idea of like, okay, well we want to unify as much as possible create modules that can be shared. but ultimately it would be great if we kind of had our own tech that was like shared across the studios. And so that was kind of the motivation for making the game engine team. [1:29:05] John: dude Cortech is sweet. I mean, it has its downsides, but it. [1:29:09] Jason J: I really liked the opportunity to kind of go in and try out things that I've been complaining about for so many years, and then trying to get a chance to like, not have those things be a problem. it was a great experience. after that I ended up joining, visual concepts where I still am, this great wild ride and opportunity that I have now. [1:29:29] John: Damn what a journey, bro. There's so much, I didn't know. J This is why I love this show. I love the opportunity that it gives me, right? for whatever reason, when I was working with a lot of you, I wouldn't take the time to connect as much as I should have. I didn't leverage the time we spent together as I should have. And it took a damn pandemic to remind me, to reach out and connect to all these cool people that I know and have interacted with. And thank you for taking the time. [1:29:56] Jason J: Thank you for having the platform. That's one of the things that I, as an engineer and I, as my own personality needed to, realize, and the pandemic effected a lot of things and it helps either clarify the picture, or really accentuate the things that are important in life. one of the things that I had not been very good at was kind of keeping in touch with the people that I worked with, the people that I respected, the people that helped mold my career. And so having this type of platform allows me to do that. Plus I get to hear your great laugh as much as I can, because I don't know what it is since. I've made you laugh anytime it's infectious. [1:30:37] Jason J: It's one of those things that I just like to hear. [1:30:39] John: appreciate that brother. It's got nothing on John street pan man. He's legendary. [1:30:43] Jason J: his, his is wonderful. And I got him definitely to almost split a gut a couple of times, but, on here. he had quite a career as well. [1:30:53] John: Yeah, dude. I think I'm going to have to wait till he retires or leaves. You know, the rockstar devs are like on gag order. [1:30:59] Jason J: he definitely is jovial person [1:31:02] John: Oh yeah. [1:31:03] Jason J: get a great conversation out of it, but maybe when you retire. [1:31:06] John: Yeah. when he, they use I'll be out there waiting, like, as soon as I hear he's changing or retiring, I'm going to John. It's time. Fall out of play. man. All right, buddy. going to hit the lightning round. Short questions, short answers. ready for this? [1:31:22] Jason J: I hope so. I will try and restrain myself [1:31:24] John: What's the last game you finished? [1:31:26] Jason J: hundred percent or just get to the end of the story. [1:31:29] John: That's a good question. I should start asking platinum trophy finish, but finish the game. Got the credits. [1:31:36] Jason J: So the last one I finished was actually a Assassin's creed Valhalla, where I got to the end of the story. The last game that I, a hundred percent was Spider-Man, the PS4 version, not miles Morales. I haven't been able to finish miles Morales yet. [1:31:48] John: That's a good one. And that was probably one of my platinum. I don't have that many platinums, but five minutes. Definitely. One of them. deserted island game. [1:31:58] Jason J: it depends on if it's a desert island where I never can escape. it would definitely be the game that actually kind of started all this that I keep, remembering whenever I reminisce about games, is Indiana Jones and a fate of Atlantis, [1:32:09] John: What console was that on [1:32:11] Jason J: that's a PC game. It [1:32:12] John: That's what I'm saying. It's not like pitfall style. [1:32:14] Jason J: if you remember the, the days of, Lucas arts [1:32:17] John: Yeah. Oh, so it looks like King's layer kind [1:32:20] Jason J: Uh, kind of, yeah, it has a similar kind of, it's a story-driven game. It's a Sierra game. it was the first game where the story would branch that I could play. Like you can, that was the first one that I played. And it really struck me because I played it multiple times [1:32:36] John: replayability. [1:32:37] Jason J: and it was like each time I was like, oh, well, what if I did this? And you know, there, there were three ways that you could play the game. And I played all three ways and I was interested at what combinations you could make. And oddly enough, I got to meet both of the designers of that game and thank them. So that was kind of a cool moment being able to do. Talk to them and say, Hey, thank you for this game. And one guy was actually getting at a conference and he was talking about another game that he had made. And I said, Hey, thank you for this game. And he was like, wow, [1:33:03] John: Yeah. [1:33:04] Jason J: I haven't heard that game in so long. It was like, kind of like a refreshing moment of like, wow. You, you know, my early work kind of thing. [1:33:11] John: I can't tell you how great of a feeling that is to be thanked for your work on the thing. that you slave for to get out into the public. So anybody listening out there, it always feels good. Take the time out. Thank you, dev. They work [1:33:25] Jason J: you know, I've had people come up and thank me for various things, uh, at times. And it's wonderful to hear it from the players. Like the developers inside can thank you as well. but having a player come up and tell you, Hey, this title changed my life or helped me engage with the world in a different way. And thank you for that. you know, sometimes when I tell them like, Hey, I didn't actually work on the gameplay stuff. They're like, I don't care. You helped to get out the door. that's what matters to me that's happened multiple times. And it's really cool when that happens. [1:33:56] John: What is the last book you read? [1:33:58] Jason J: The last book I read, it's a programming book actually. [1:34:01] John: Hey, I like those. [1:34:03] Jason J: There there's a series of books called the clean coder series there's a progression of books. There's clean coder, clean architecture, And I read the clean architecture book most recently, and that one was helpful. I've gotten deeper into kind of the nerdy kind of non Ganey side of programming C plus plus, and things like that. So I'm reading a lot of books that are not directly about games, but are about C plus plus that we use to make games. [1:34:30] John: Hey man, you're Well, past your 10,000 hours in mastery, man. So there's only so much more to go. [1:34:35] Jason J: I'm always learning. So, you know, and things are always changing. So there's always a new challenge. [1:34:40] John: What is the thing that you enjoy the most about engineering on games? [1:34:44] Jason J: so there's two things. one that is solving the problem. Like I like solving the problems and kind of feeling like, I feel as though a cleanliness washes over you when you solve this problem that you've been tracking for so long. and then there's the interaction with the content creators, the spark that you see when they actually click a button and it does something for them [1:35:04] John: yes. [1:35:05] Jason J: like their eyes light up and they just have this surge of creativity. I love seeing that. [1:35:11] John: Yes. I get a little bit of that taste as a tech designer, but yeah, I can imagine, man. That's fantastic. What, if anything, do you miss about being in the office? [1:35:20] Jason J: I guess the things that you kind of started this podcast about you know, I took for granted cause out of the interactions that I had there and, while I, wasn't kind of having my personal life kind of cross over into the interactions that I had, there was a, a place where you could go have interactions with folks about programming, about whatever, and it wasn't necessarily business oriented. And the, I guess the term would be kind of the, the cooler talk. Like you go to the water cooler and you're talking about some sort of programming thing, or someone's talking about the game that they played or the experience they had and you don't really get that as much at home. [1:36:00] Jason J: some of that is leadership as well. So some leadership, choices are around kind of having these kind of open forum, like zoom calls, where you get in and it's like, we're all just kind of in the zoom call, hanging out together. And conversation can either kind of spring up from that. Or there's a moment where you can kind of see the other person and be like, okay, we're kind of in the office a little bit. [1:36:19] John: that was a key pandemic survival mechanism that a lot of teams were trying to implement. Right. At least like virtual happy hours or whatever. Curious. Is there anything you're doing on your team to give an outlet for that? [1:36:30] Jason J: one of the things that we're doing now is more kind of just having a place for people to kind of talk And it's, it's a weird thing because we don't have that mandatory, like, Hey, here's a room that you go into to kind of have those conversations. But I think there's a, encouragement to kind of engage and talk like, Hey, you're running into this problem and kind of have those kind of BS time periods where of just hanging out, like talking to each other. [1:36:57] John: Are these like blocked out in the calendar at all or something? [1:37:00] Jason J: so I've had it where they are. but it's happened where. If there isn't something to talk about, the engineers start talking about the bug that you're trying to solve. And so there's like some kind of pressure that you need to put on to say like, Hey, you know, we're not talking about this [1:37:14] John: Yes. [1:37:15] Jason J: we're, kind of trying to hang out and then everyone gets quiet all of a sudden. And so then you got to like, okay, well, you know, you gotta throw out something. [1:37:21] John: Yeah. Some icebreakers are always handy. you weren't doing this, what would you be doing? Right? Let's say it was It could be this year. It could be the fifties. Forties. [1:37:32] Jason J: I don't know, I mean, there is a thought experiment that I've done from time to time when evaluating my career and the trials and tribulations that I've gone through is like, if you had infinite money and everything is taken care of what would you do? a lot of people say like, oh, I travel the world, blah, blah, blah. But eventually you've done all that. What do you do then? I keep going back to, I want to program, I want to make games. And so if I wasn't doing this, I would probably be doing some job to pay the. And then doing programming or doing games, making games, playing games, doing kind of the things that you see, all the Twitch people doing now, like casting and all that stuff. [1:38:14] Jason J: even though I'm not a huge personality that some of the casters are, I would probably do the YouTube stuff for a game, like I'm playing a game and we're talking about playing the game and all that. Cause I like that world. [1:38:25] John: I like it. I would've never had anticipated that. And now I'm kind of smiling, hearing that what's something most people don't know or would be surprised to know about UJ. [1:38:36] Jason J: I think something that we touched on earlier in the conversation, which is when I ask a question about you about your past, I am generally interested in learning about you. So I grew up in a very small town [1:38:46] John: I think that's something to do with it. [1:38:48] Jason J: there's a super superficiality that kind of the city folk have as it were, as I stereotype yourself who asking all the questions, where, people will ask things and they just really don't care. They're just doing it to try and be polite. And, I am curious because everyone's perspective kind of builds who they are and someone's perspective is something that. Only they have. And if they share it with you, is something that is extremely valuable. [1:39:19] John: You're absolutely right. There's not enough people that know how to listen. There's people that ask questions and are essentially just waiting for their turn to talk. I wonder if that is an element of being from Weimer, Texas, a town of less than 2000 people or what, but it's definitely a beautiful thing about who you are. [1:39:38] Jason J: yeah. It can lead to trouble in meetings sometimes because you are waiting for your turn, but then the conversation moves on and they don't like the leadership or whoever's running the meeting doesn't necessarily have the same mindset. So they're not trying to give people that forum or to get those different perspectives. They're just like, okay, we solved this problem. Then they move on. I have seen that happen in meetings. So it is a thing too. [1:40:02] John: I know that time is always a thing and a factor of meetings, right? Like more people in a room, more money being burned, but especially in the pandemic where it's a zoom room and, you know, you have the little Hollywood squares of people. I like to encourage leadership and managers and producers. Call on people and make sure that everybody's voice is heard. Right. Otherwise, why the hell are they in the meeting? You know what I'm saying? You could just send them the recording. So if they showed up to the meeting, give them Invite them in to talk. [1:40:30] Jason J: Yeah. And some of it is just as simple as just asking for their input, for team members that are of groups that are less representative in engineering, just giving them that forum and platform and saying like, Hey, what do you think can lead to all kinds of good things? So there is a moment that as a leader or a person running the meeting, you kind of have to be cognizant of, but it's still a thing that I wish was kind of more ingrained in people and is ingrained in me and I've gotten burned by it. And at times, because I'll have that mindset and then just the meeting won't have that mindset. [1:41:03] John: You've worked on RTSs shooters, wrestlers. You've been an entrepreneur. Is there anything left for the type of game you'd love to work on given the chance the franchise or IP you'd love to work with a group of people or a team? [1:41:22] Jason J: there are kind of a handful of people and it's like, Hey, you know, if I were to start a studio and they were willing to come join me, I'd love to work with these folks. I'd kinda like to work on an RPG, [1:41:32] John: like a J RPG or like a BioWare RPG. [1:41:34] Jason J: more like a BioWare RPG. [1:41:36] John: I was going to lean into that, like that. Choose your own adventure. Create your own narrative [1:41:40] Jason J: yeah. Specifically I would really love to do a nice deal Republic type title. [1:41:45] John: Oh shit, dude. [1:41:47] Jason J: of my favorite games of all time, and it would be great to kind of make something in there, [1:41:52] John: If that game didn't have the star wars theme on it, would it still be as good? [1:41:56] Jason J: the star wars theme made it, the thing that I would buy, that, game came out while I was still in school and it came out on Xbox. And I was waiting for the PC poor. And one of the team members that I had at full sail said, this game is too good. I'm going to give you my Xbox so you can play it. And so it was like, okay, I have to play this game. And, if it was a different theme, I don't know if I would have been drawn to it as much, I might've given it. it's due, just later on, not right away. [1:42:24] John: that game is widely renowned and special and beautiful and That'd be cool to have you back at EA working on those types of games, but future who knows what will happen. where can people connect with you? Reach out to you, see your work? Is your team hiring [1:42:41] Jason J: my team is hiring, we have a posting on the, visual concepts website, uh, for LA. go check it out. I have a LinkedIn, I have been fairly curating it. Like there's been people that try to connect all the times like recruiters and things like that. And I've been a little bit more hesitant to just accept everybody, uh, because there is a little bit of guardedness to your kind of core. Group of people that you want to kind of keep in contact with and kind of just opening the flood gates can treat weird scenarios where you have a guy on your list. You're like, how did I get that guy on my [1:43:12] John: I I'm the same way I have my LinkedIn. Blocked. Like if you don't know my email, you can't hook up with me until two that send a note. If you're going to try to link up with Jason, [1:43:23] Jason J: Yeah. [1:43:23] John: why you're connecting, how you heard about him. [1:43:26] Jason J: those of you that may be out there that are in school and getting in through college and things like that. Like I have reached out to various programs like that in the past to give advice and talk to people. I've been a, an advisory member on a, on a college program, as well as kind of come and given presentations at universities or high schools to be like, Hey, this is what I do. This is how I got into this. So that is something that, don't be scared to reach out if you are someone that, isn't already in the game industry. And you're curious about how to get in. [1:44:00] John: There you go. There's your invitation. Okay, Jay, you know, what's coming. Who do you nominate to fall out of play area behind you. [1:44:08] Jason J: So I have two people for you and they have, they have, both agreed to do this. [1:44:12] John: shit. [1:44:13] Jason J: Yeah. So now you're in trouble. [1:44:14] John: got the pre-approval that's that's what's up? [1:44:16] Jason J: Yeah. I don't want to throw names out and they're going to look at me and go, why did you do that [1:44:19] John: that's happened. [1:44:20] Jason J: both people came from my very first job, big, huge games. So it's a deep cut. They both have kind of done different aspects of game development than me. one is, has their own company and they're doing UX. his name is Jason Sklar. and then the other person was a producer when I was at big huge games and has kind of risen to the rank of COO at a company. her name is Erin Krell. [1:44:45] John: man. I don't interact with enough. COO's out there. [1:44:48] Jason J: their interactions set me up on the road that I'm on and whether I gave them enough credit or not, they kind of helped me into where I'm going. [1:44:57] John: Hey, well, now's your chance. Hopefully they listen to this and they know it's a ingrained forever in the audio banks of the internet. Jay, this has been fantastic, bro. Are there any closing words for the people listening out there? [1:45:10] Jason J: so one thing that my grandfather told me a long time ago that has stuck with me and I use in every interview I've ever gotten to is you never stop learning. Your education is something that no one can take away from you. Someone can come and take your car. They can take any sort of material item that you have. But if you learn something, no one can take that. [1:45:29] John: Boom, I love that. you weren't the most passionate student, but you've definitely never stopped learning, signing up for degrees upon degrees and journeying to schools and diving into different technology and whatever you needed to, and even given the chance to not do it. still inquiring and learning about people around you. That's what's up. Thank you. Jay. Till next time, friend. Peace. Our first full-time engineer episode is in the books episode 29. And WWE two K 22 is out. I'm going to be looking to pick up a copy to support the homie. It appears to be getting pretty nice at claim and being well received as a great leap above what two K 20 did like three years ago. [1:46:15] John: And it's benefited from being an extra year in the oven. Jason's given me a run for my money. I thought I had touched the most engines in the game, but he's got me beat. His tail has a resounding message of how his interests along with his teachers and friends eventually end even as parents, right? They eventually got him steered onto his professional calling in programming and engineering. So much soul to the point where, when I asked him, you know, what would you be doing if you weren't doing this? He's still like, yo. I would be doing it. I can't see my life without it, even if it is a hobby. Even if I was doing something else to make money, I was still be doing this on the side. [1:46:50] John: He's in so much backend engineering and gameplay. He's got such a wide. Wide breadth of experience and. Still reading his craft and still putting hours into mastery squared. That I'm curious when he might make another plunge and strike out again to build. Maybe his own studio. That'd be super interesting. And. I wouldn't be surprised if it happens. We got deep onto some burnout. I think that's always an issue. That's going to face anybody. Who's been doing this for long enough and It'll be fantastic to get to a 0.1 day in the future where we can look back on this thing as a legacy of how we used to things, but for now, you know, it's still a very real thing. [1:47:28] John: And. It's a story that is worth continuing to tell onward and forward to remind people that. It's a very real thing and we can always do better about handling it. It's safeguarding it and spotting the warning signs, especially as we work from home. Right. This is kind of a new frontier. That will sneak up on us and it is a business and while delaying a game because of the difficulties of building a thing from home, Is an option, how long can you do a thing? It's worth the continued conversation for sure. On episode 30, you know, I try to bring a deer homie out for every 10th episode and 30 is no exception. So we need to sit down with design director over at poly arc, another fellow full sail alumni. [1:48:11] John: And, uh, not long till the end who shifted the multiplayer on red dead redemption. Got to break in by working on midnight club and got to take his talents on to mobile, tiny racer. And now up here in Seattle. Putting in that work at poly arch on mosque one. And mosque too is coming out in a couple of weeks on Monday, April 11th. 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. [1:49:01] John: 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. Next time. I'm your host John Diaz until next time devs stay strong. Stay true. Stay dangerous. Mega ran. Bring them home.