System Integration Quotes

Complexity that works is built up out of modules that work perfectly, layered one over the other.

What we're really trying to do is have heterogeneous systems really become the foundation of our computing going forward. And that's the idea that you make every processor and every accelerator a peer processor.

People who are really serious about software should make their own hardware.

My list of basic tools is a partial answer to the question about what has changed: Over the past few years, large numbers of programmers have come to depend on elaborate tools to interface code with systems facilities.

We think Android is very, very fragmented, and becoming more fragmented by the day. And as you know, Apple strives for the integrated model so that the user isn't forced to be the systems integrator.

There will never be a day where the depth of integration, unless it was all built from the bottom ground up, will be integrated as any of us would like.

When I worked at Microsoft, I got to go and visit a bunch of different companies. Probably a hundred different companies a year. You'd see all the different ways they'd work. The guys who did Ventura Publisher one day, and then United Airlines the next. You'd see the 12 guys in Texas doing Doom, and then you'd go see Aetna Life Insurance.

There's no other company that could make a MacBook Air and the reason is that not only do we control the hardware, but we control the operating system. And it is the intimate interaction between the operating system and the hardware that allows us to do that. There is no intimate interaction between Windows and a Dell notebook.

By the time I got into test work, it was dying out. It wasn't really flight test at all; it was mostly testing new gadgets.

But how does it feel to plug into a system that's say, a million times as smart as a person.

When I started at Microsoft, I was lucky enough to be part of the rise of the client-server paradigm.

Hardware: where the people in your company's software section will tell you the problem is. Software: where the people in your company's hardware section will tell you the problem is.

My impression is that a really, really high-order concern for the whole development community is interoperability and consistency.

Putting Windows [3.11] on top of DOS is like putting whipped cream on a road apple [horse poop].

We think of enterprise architecture as the process we use for fully describing and mapping business functionality and business requirements and relating them to information systems requirements.

What's important for all of us as chip companies is to keep the innovation going: putting out new products, figuring out how we connect these complex systems.

Well, I mean, we are developing the other parts, and we can't give quite all our attention to the upper part, but soon the lower parts will be developed, and the upper part and the lower part will become partners, that will be wonderful.

Management does not know what a system is.

One of the things that Java is good at is giving you this homogeneous view of a reality that's usually very heterogeneous.

Information technology departments must spend enormous amounts of time and money worrying about integrating big computer systems with billions of pieces of customer data.

I will take the best from each system and introduce it in Russia..

You definitely go through a stage, most coaches do, where you see a good player and you get enamored, you really like what the player does, but then when you put him into your system, it's not quite the same player that he was in another system. He has some strengths, but you cant utilize all those strengths. If you try to utilize all his strengths, you end up weakening a lot of other players who are already in your system.

Software is inherently complicated. If you say to somebody I want an airline reservation system, to really say what you want in terms of overbooking and fares, and different airlines communicating with each or schedule changes, it's immensely complex. And so you can't write a program that's any simpler than that full specification.

Silos can't interoperate unless the technology does.

Infrastructure web services had to happen.