Yukihiro Matsumoto Quotes

Ruby inherited the Perl philosophy of having more than one way to do the same thing. I inherited that philosophy from Larry Wall, who is my hero actually. I want to make Ruby users free. I want to give them the freedom to choose.

I believe consistency and orthogonality are tools of design, not the primary goal in design.

A rational model of software is to design it quickly - the economic pressure to improvise presents an interesting challenge.

The problem is, in software design, often the consequences of your decisions don't become apparent for years.

The critical thing in developing software is not the program, it's the design. It is translating understanding of user needs into something that can be realized as a computer program.

We shifted our philosophy from being a computer mapping group that would support planners to the idea of building actual software that would be well engineered. Because at that time, our software was not well-engineered at all; it was basically built with project funding and for project work, largely by ourselves.

There are two methods in software design. One is to make the program so simple, there are obviously no errors. The other is to make it so complicated, there are no obvious errors.

After all, C++ isn't a perfect match for Java's design aims either.

The only thing Martha and I have in common is that we both used to model. Martha Stewart is extremely talented. Her designs are picture perfect. Our philosophy is life is messy, and rather than being afraid of those messes we design products that work the way we live.

The payoff of a customer-centric approach to software and digital product design is substantial and long-lasting for both companies and their customers.

Design is not for philosophy it's for life.

Sun's role in the grand scheme of development is to work on the runtime environment and the APIs. The tools we produce are much more for systems programmers, not enterprise developers.

I felt there was a need for us to build a new programming language. I also had come to see that Microsoft functions best when it controls its own destiny.

C is peculiar in a lot of ways, but it, like many other successful things, has a certain unity of approach that stems from development in a small group.

When you design a building, you start from a general philosophy, and you come down, and you start from detail and come up. Only the theoretical architect believes that you can make the concept and then sometime, somebody will come to build it.

When I announced the development of Perl 6, I said it was going to be a community design. I designed Perl, myself. It's limited by my own brain power. So I wanted Perl 6 to be a community design.

Everyone by now presumably knows about the danger of premature optimization. I think we should be just as worried about premature design - designing too early what a program should do.

It's strategic for us - lots of people will develop applications in .NET.

Received wisdom is that if you spend time up front getting the design right, you avoid costs later. But the longer you spend getting the design right, the more your upfront costs are, and the longer it takes for the software to start earning.

Martha Stewart is extremely talented. Her designs are picture perfect. Our philosophy is life is messy, and rather than being afraid of those messes we design products that work the way we live.

I'm surprised sometimes at how some of my actions are misinterpreted.

My design philosophy has always been eclectic.

My design philosophy is to make women feel like peacocks.

Porsche's and Apple's design philosophies are similar. Much like the 356, the original iPhone was about defining a foundation for the future.

When you're designing and inventing the way I did, every minute of your life is put - every neuron in your brain into trying to think about the little code and how you can maybe have one less line of code and a little bit more straightforward from the beginning to the answer. And you don't have time to think about companies and products and how would I build this. So Steve Jobs and I were a very necessary pair.