Satoru Iwata Quotes

I think it's a combination of technical and social factors that leads to all the defects in deployed software.

There is a strong movement towards increased accountability for software developers and software development organizations.

When we got ready to ship out Firefox 1.0, the last set of things we did was to make it appealing to a consumer, to add the polish of a world-class product to it.

Like any well designed software product, Windows is designed, developed and tested as an integrated whole.

If we launch a new product, we have to time it right. It's not about how soon you can do it but how well we can do it.

The process of software development doesn't feel any better than it did a generation ago.

When someone builds a bridge, he uses engineers who have been certified as knowing what they are doing. Yet when someone builds you a software program, he has no similar certification, even though your safety may be just as dependent upon that software working as it is upon the bridge supporting your weight.

I found out that most programmers don't like to test their software as intensely as I do.

Running the test suite like this allows us to catch problems when they are just introduced.

This will surprise some of your readers, but my primary interest is not with computer security. I am primarily interested in writing software that works as intended.

After releasing Mono 1.0, we started work on a new edition of Mono that will be released later in the year.

If I say I've got two versions of Word - that old one from 1982 that's perfect, with zero defects; or the new one that's got all this cool new stuff, but there might be a few bugs in it - people always want the new one. But I wouldn't want them to operate a plane I was on with software that happened to be the latest greatest release!

I don't micromanage, but I do care deeply about every product we make. Every one goes through me, and I try most of our products before they go to market, including our John Paul Pet flea and tick shampoo. If I don't like it, it's not coming out.

All software sucks.

We plan to support Exchange 2003 as soon as it is released. We already have the prerelease versions from MSDN.

Developer testing is an important step towards accountability. It gives developers a way to demonstrate the quality of the software they produce.

Indeed, the woes of Software Engineering are not due to lack of tools, or proper management, but largely due to lack of sufficient technical competence.

It's healthy to have two or three weeks' gap between big releases.

You have to have great products out at the right time. It's difficult to go with one foot on the gas and the other a little bit on the brake.

I've seen promotions rush things to market and not be strategic about it. The first impression is the lasting impression.

In the end, we don't believe in launching any type of product if it isn't perfect in our eyes.

In software speed to market, speed to learning is really key. In hardware if you screw it up you are dead. So accuracy really matters.

Not only because the product wasn't a great product, but remember it took us five or six years to ship it. Then we had to sort of fix it. That was what I might call Windows 7.

There are no significant bugs in our released software that any significant number of users want fixed.

When you develop software, the people who write the software, the developers are the key group but the testers also play an absolutely critical role. They're the ones who ah, write thousands and thousands of examples and make sure that it's going to work on all the different computers and printers and the different amounts of memory or networks that the software'11 be used in. That's a very hard job.