Episode #467 from 1:20:32
John Carmack
John singularly has this intense dedication to getting the best result from his code and having absolutely no attachment to passcode and some of the legendary things he did. The end result was an absolute breakthrough in real-time computer graphics, weren't his first try. They were like his seventh or eighth try after he'd done something time and time again, tried it, found a better approach, thrown out the old one, built it again, and continually rewrite his code until he found the absolute best solution to a problem. I think that stands as a lesson for every programmer to pick up on. When something is really, really important, its performance is absolutely critical to the product or its quality or its capabilities. Just iterate on it until you've achieved perfection and don't settle for the first or second solution is good enough. The result of that both you and him sort of define the future of gaming, of gaming worlds. It's so beautiful to see. It's just fascinating. It's inspiring because under so much uncertainty, under so many constraints, you figure out a way. That actually continues to this day because yes, the hardware is improved incredibly, but in order to create an ultra realistic, highly dynamic, real time rendering of the world around us, it's still really, really difficult. There's all these kinds of optimization, like you mentioned. Maybe you can speak to that Unreal Engine One journey from one to 5.5 or .6 now. For 30 years, you've been creating virtual worlds. What's it like evolving a game engine for those 30 years when the hardware under you is improving exponentially? What are some things that changed and what are some universal truths that have not changed?
Why this moment matters
John singularly has this intense dedication to getting the best result from his code and having absolutely no attachment to passcode and some of the legendary things he did. The end result was an absolute breakthrough in real-time computer graphics, weren't his first try. They were like his seventh or eighth try after he'd done something time and time again, tried it, found a better approach, thrown out the old one, built it again, and continually rewrite his code until he found the absolute best solution to a problem. I think that stands as a lesson for every programmer to pick up on. When something is really, really important, its performance is absolutely critical to the product or its quality or its capabilities. Just iterate on it until you've achieved perfection and don't settle for the first or second solution is good enough. The result of that both you and him sort of define the future of gaming, of gaming worlds. It's so beautiful to see. It's just fascinating. It's inspiring because under so much uncertainty, under so many constraints, you figure out a way. That actually continues to this day because yes, the hardware is improved incredibly, but in order to create an ultra realistic, highly dynamic, real time rendering of the world around us, it's still really, really difficult. There's all these kinds of optimization, like you mentioned. Maybe you can speak to that Unreal Engine One journey from one to 5.5 or .6 now. For 30 years, you've been creating virtual worlds. What's it like evolving a game engine for those 30 years when the hardware under you is improving exponentially? What are some things that changed and what are some universal truths that have not changed?