Episode #467 from 6:56
Advice for young programmers
10 to 15,000 hours. What was the value of the hours as a kid you put in in programming that led to the success you've had in later life? Maybe this is by way of advice to younger people in terms of how they allocate the hours of their early life. Yeah, it's not just hours. It's really striving to learn, to understand what knowledge you have, what knowledge you lack, and to continually do experiments and work on projects that improve your knowledge base. And I didn't do this with a great amount of structure or planning. I was rather just going from project to project, doing things that I thought would be fun and cool. And with each project I learned new things, learning about how to store and manage data, learning how to deal with advanced data structures, how to write complex programs that have deeply nested data and control flow. Each one of those provide a lesson which were later essential. In 1991, I released my first game and over the course of that decade went from zero commercial releases to the first generation Unreal Engine. But this was largely just using the knowledge that I'd built up over the previous decade, just doing fun hobby projects. And if I hadn't done all of that work, there's no way I could have ever built the things that came later.
Why this moment matters
10 to 15,000 hours. What was the value of the hours as a kid you put in in programming that led to the success you've had in later life? Maybe this is by way of advice to younger people in terms of how they allocate the hours of their early life. Yeah, it's not just hours. It's really striving to learn, to understand what knowledge you have, what knowledge you lack, and to continually do experiments and work on projects that improve your knowledge base. And I didn't do this with a great amount of structure or planning. I was rather just going from project to project, doing things that I thought would be fun and cool. And with each project I learned new things, learning about how to store and manage data, learning how to deal with advanced data structures, how to write complex programs that have deeply nested data and control flow. Each one of those provide a lesson which were later essential. In 1991, I released my first game and over the course of that decade went from zero commercial releases to the first generation Unreal Engine. But this was largely just using the knowledge that I'd built up over the previous decade, just doing fun hobby projects. And if I hadn't done all of that work, there's no way I could have ever built the things that came later.