Isaiah Thomas Quotes

During my tenure with Nintendo, we've pushed back development a number of times on key games - in the end, it's always worth it - because our focus on quality is so strong.

I think the journey of making a game... we want to enjoy that process.

Game development is very difficult. Nobody sets out to create a game that's not fun. It's all of the challenges and difficulties that happen throughout development that determine whether a game is a failure or a success. I think playing those thousands of games is the single best and easiest way to learn from my predecessors.

But typically for a project like the Mac, the size we had was pretty good. And it has different stages. The team grows as you have to write manuals and do testing... though the Mac had no formal testing.

Program construction consists of a sequence of refinement steps.

You can’t really understand the challenges involved with any major tech project until you start trying to build it.

A very important part of game development is testing - something that a lot of developers don't do.

Extreme programming is an emotional experience.

We didn't have our online service developed. We had never shipped a console game before as a company. So we were developing a lot of new competencies as a company and assembling a new team.

On a Bioware game, if I say anything that's not on the page, It would create a bug in the system, and it would kick back, and I would have to do it again due the technical demands they deal with.

I'm a big gamer. I know the lead time and how long it takes to develop a game and how hard it is to get it right.

Building technical systems involves a lot of hard work and specialized knowledge: languages and protocols, coding and debugging, testing and refactoring.

My earliest interest in game design came when I was in primary school, and my parents bought a Commodore 128 computer. I taught myself to write programs in BASIC, and then I made my own games.

Most of the work performed by a development engineer results in failure.

Software development is technical activity conducted by human beings.

First, I take a lot of time to just explain my vision of what the game should be to the team. Then I make all subsequent decisions based on how I want to feel when I buy the game, and what impressions I want to have of it. I then go about implementing the little points that will lead up to that finished product.

God of War' was a 40-60 person team. It was a lot of very different, very passionate, very crazy people.

Time makes a bigger difference: just making a game, shipping it, looking at what you did, how you did it, what you did well, what you didn't do well, and doing better.

When you're limited on parts and you have reliability issues, you don't get the testing done. You need to really develop the car.

I would play games long enough to discover what games were doing and how they were doing it. And then I'd spend the rest of my time building.

I've never made a game for a high-definition platform. That's definitely something I'm interested in.

'Fallout 76' and 'Blades' get a lot of my time right now. I'm in more meetings as it's gotten bigger.

There are lots of people at our company who dedicate their time and effort to make sure that the journey from product design to hitting the screen is as seamless as possible.

Being a director, I've had the privilege of heading a PS3 launch title. Looking back, I think the PS4 has made the development cycle much easier.

I do a project and then I forget about it because the release of whatever work you have done is not in your hand.