What important tech are you not yet sure will work?

That's a great question, because it's kind of our job to know how each... That's a tough one. I'm going to have to think a couple minutes about that, and in doing that, I'll just fill the air with words. Normally, our job is to know how we're going to attack something. And very seldom do we just jump into something and have zero idea, with a naive level of development. The stuff that scares me the most is the stuff that we don't know that we don't know. And I know that sounds kind of nebulous, but that's the stuff that bites us: when you don't know about a problem that's going to be coming. Because if you already know that this problem is going to come, we can come up with some sort of solution, and we've done that in almost every case.

That's universal to all game development.

Absolutely. All human thought, really. And those are the things that scare me the most. So if I was to answer the question, I would say the stuff that we have not yet seen that is going to be a problem, that's the stuff that I'm the most worried about, and that I don't know how to solve, because I don't know what the problem is.

That's one of the reasons why they call it game development, not game building. There's no blueprint at the very beginning. We're not just building what somebody else has already figured out, just A to B to C to D. We are discovering and exploring the solutions and the options that we have towards making the game throughout the entire process, and we will be right up to the point where we release the game, and even after that.

Yeah, absolutely. Most of us want to just keep building up on stuff. If any one of these developers got six months to work on one thing, they would come up with so many different things. And again, it's really about triaging how much time you can allow them to spend on certain pieces of tech.