korrents

What Tim Sweeney thinks about design

@tim-sweeney · 22 positions · 0 changes of mind

Founder and CEO of Epic Games, creator of the Unreal Engine and of Fortnite.

Tim Sweeney did not write this page.

We collected these quotes from things they published elsewhere, and every quote links to where it was said. They have no account here and have not endorsed this site. Quotes are word for word; the short line under each one is our own restatement, not their wording. Their own site. Is this you? Claim it or ask us to remove it. Or tell us what is wrong here.

10 dated positions, 2025, in their own words. Our reading of what Tim Sweeney has said — not written or endorsed by them.

10 positions so far — this page is not yet offered to search engines.

  1. Our readingMost of the pain a beginner feels while learning to program is not the difficulty of the craft but the failure of programming language design.

    Their wordsA lot of what they're facing isn't the challenge of learning a new art. It's friction introduced by failures of programming language design.

    ↗Tim Sweeney: Fortnite, Unreal Engine, and the Future of Gaming | Lex Fridman Podcast #467youtube.com 1st of 22 in this recording

  3. Our readingSociety keeps rebuilding itself around credentials, but the companies that build great things hire the people who do great work, not the people with the certificates.

    Their wordsThere's ever more pressure to rebuild society more and more around credentials. Do you have this certificate? Do you have that proof? But companies that are focused on just building great products and doing great things gravitate towards people who do the great work.

    ↗Tim Sweeney: Fortnite, Unreal Engine, and the Future of Gaming | Lex Fridman Podcast #467youtube.com 2nd of 22 in this recording

  5. Our readingIteration speed is the decisive factor in making a game: a team that rebuilds every day ends up far better than one that rebuilds every week.

    Their wordsWe'd constantly be improving the tools and just the iterative process and the speed at which that improves products is the critical element to success in games. The slower the iteration cycle, if you make a build every week and you prove, you go through one iteration every week, you're going to be way way way worse by the end of your project than a game company that makes new stuff every day.

    ↗Tim Sweeney: Fortnite, Unreal Engine, and the Future of Gaming | Lex Fridman Podcast #467youtube.com 5th of 22 in this recording

  7. Our readingUnreal Engine's deepest limitation is that game simulation still runs on a single core, because single-threaded programming is orders of magnitude easier than multi-threaded.

    Their wordsThe biggest limitation that's built up over time is the single-threaded nature of game simulation in Unreal Engine. We run a single-threaded simulation. If you have a 16 core CPU, we're using one core for game simulation and running with the complicated game logic because single-threaded programming is orders of magnitude easier than multi-threaded programming.

    ↗Tim Sweeney: Fortnite, Unreal Engine, and the Future of Gaming | Lex Fridman Podcast #467youtube.com 6th of 22 in this recording

  9. Our readingAI writes code well only where a million repositories have already written it; getting it to do something genuinely new remains notoriously hard.

    Their wordsAI is really great at spewing out code that does something that a million GitHub repositories already do because it's learned the underlying pattern. It's notoriously hard to get to do something new that hasn't been done before, especially when it's a complex task.

    ↗Tim Sweeney: Fortnite, Unreal Engine, and the Future of Gaming | Lex Fridman Podcast #467youtube.com 9th of 22 in this recording

  11. Our readingThe existence of boilerplate code is itself a failure of programming language design and of software modularity, not a job for AI to take over.

    Their wordsThe topic of boilerplate code is an interesting one because the mere existence of boilerplate code is a failure of programming language and of the idea of creating software modules.

    ↗Tim Sweeney: Fortnite, Unreal Engine, and the Future of Gaming | Lex Fridman Podcast #467youtube.com 10th of 22 in this recording

  13. Our readingThe metaverse does not require VR: VR is hardware that may or may not improve the experience, and it has a much smaller audience than social gaming already does.

    Their wordsVR has a much smaller audience. I don't think you need VR to have anything like this. VR is hardware that may or may not enhance the experience for some usage cases.

    ↗Tim Sweeney: Fortnite, Unreal Engine, and the Future of Gaming | Lex Fridman Podcast #467youtube.com 12th of 22 in this recording

    video games

  15. Our readingWhat a shared digital economy needs is interoperability, not cryptocurrency: a database or a standards body does the job, exactly as railway standardisation did.

    Their wordsWhat you need is interoperability. Interoperability can happen through a blockchain, it can happen through a database, it can happen through standards bodies with defining standards and protocols. And we've been doing it for hundreds of years since the railroads were standardized. And it's not something that totally requires a novel technological solution.

    ↗Tim Sweeney: Fortnite, Unreal Engine, and the Future of Gaming | Lex Fridman Podcast #467youtube.com 13th of 22 in this recording

  17. Our readingThere is one right way to build a type system, the way that gives you mathematical proofs, and every other kind of type system is simply worse and should be rejected.

    Their wordsBut there are other parts of programming languages that are not subjective but should be fundamental. And when you look at type systems, there is a way to do type systems that gives you mathematical proofs. And every other way of type systems that doesn't give you mathematical proofs is just worse and should ultimately be rejected.

    ↗Tim Sweeney: Fortnite, Unreal Engine, and the Future of Gaming | Lex Fridman Podcast #467youtube.com 15th of 22 in this recording

  19. Our readingConcurrency should stop being the programmer's problem and become the language designer's: it is better to impose vast pain on a few people than on a million.

    Their wordsAnd by doing this, removing this from being a programming problem for the programmer to deal with, to being a language problem for us language designers to deal with. And we're moving a vast amount of pain that would be imposed on a million people, instead to a vast amount of pain imposed on a small number of people to have to actually make this work.

    ↗Tim Sweeney: Fortnite, Unreal Engine, and the Future of Gaming | Lex Fridman Podcast #467youtube.com 16th of 22 in this recording