Masi Oka Quotes

People who work on the user interface side need to have empathy as a key characteristic. But if you are writing device drivers you don't really need to understand humans so well.

I'm a designer, but I rely on programmers to bring my ideas to life. By learning to code myself, I think I can make things easier for all of us. Similarly, I want to be able to build things on my own without having to bother a programmer.

Our job as the game creators or developers - the programmers, artists, and whatnot - is that we have to kind of put ourselves in the user's shoes. We try to see what they're seeing, and then make it, and support what we think they might think.

Before I became a game designer, I was a software engineer.

We didn't do a square ball in 'Pong' because we thought it was cool. We did it because that was all we could do.

Once the product's task is known, design the interface first; then implement to the interface design.

I'm not the expert on the great gameplay. I come in for the character design, monsters, atmosphere. I'm not the technician.

Information design has been around since the 1970s. Pioneers like Yale University design guru Edward Tufte and design agency Pentagram have long known and used its power. But now with the rise of the Internet, it's having something of a second birth.

Computer programming is pretty much guaranteed income. I'm good at it, and I like it.

Our developers will make great games for whatever high-end platforms exist.

I am now very interested in computer technology as it is used currently to make games. I think this technology is very powerful and could be used in new ways.

Our developers are constantly thinking about, 'How do I bring new and novel experiences to our platforms?' whether it's the Switch, 3DS, or even a smart device. So that is just part of the way our developers think.

The very first game I worked on was for DreamWorks Interactive's 'The Lost World: Jurassic Park.'

Epic started out with scripting languages in the first generation of the Unreal engine in 1998. I wrote that. There's a place in my heart that comes along with the simplicity of programming in a scripting language.

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.

Before coming to Congress, I worked as a computer programmer and a systems analyst.

I've spent my whole life worrying about the human-computer interface, so I don't want to suggest that what we have today is even close to acceptable.

When somebody has learned how to program a computer ... You're joining a group of people who can do incredible things. They can make the computer do anything they can imagine.

One problem we discovered, for example, was that our "create a new account" button was in the wrong place...By simply moving it to the left side, mirroring the way people read, we saw a huge improvement in the way people used the site.

My number one piece of advice is: you should learn how to program.

The purpose of most computer languages is to lengthen your resume by a word and a comma.

Throughout the history of game development, the game control mechanism has become more and more sophisticated, ... Perhaps those who have quit gaming or who have never played games look at the game controller and think it's too difficult to play, even before they dare to touch it.

Asking others for input puts you in the driver's seat, and may feel less awkward than having to watch yourself on video.

I think everyone should learn how to code.

If this is preparation for life, where in the world, where in the relationship with our colleagues, where in the industrial domain, where ever again, anywhere in life, is a person given this curious sequence of prepared talks and prepared questions, questions to which the answers are known?