Modular Design Quotes

I think 'Disney Infinity' is exciting. It's hard to even call it a video game, because it's so different. What excites me about this is how it's going to put more and more of what happens in the game into the hands of the user; it's up to them. You can play it to where everything's laid out for you.

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

I think the major good idea in Unix was its clean and simple interface: open, close, read, and write.

I have absolutely no idea about space exploration. I'm a software guy. But because I'm a non-expert, I've been able to bring the software concept of modularity into the space sector, which was never done before.

Although prefabrication has a long history - the ancient Romans shipped pre-cut stone columns, pediments, and other architectural elements to their colonies in North Africa, where the numbered parts were reassembled into temples - the idea took on a new impetus with the technological advances of the Industrial Revolution.

People are building the software and so having the pieces be such that a single person understands all the tradeoffs and everything that's going on in a piece is extremely valuable. It avoids getting into an experimental mode where you're just trying things out. That never works.

Since I got involved in Telco, we first developed the first modular truck, the 407, then the 709, and now the 2213. These trucks broke away from the old face of Telco trucks. I was also just as much involved with the Safari, but nobody talks about the Safari. My involvement has been there with all Telco's projects -somehow the car has got hyped up.

I'm going to design the container and interior spaces. You bring your own stuff to it and make it your own.

If something is easy to repair, it is easy to construct.

Modularize, don't customize. Build a platform as opposed to building all of the custom technology and custom vertical experiences.

There are a variety of techniques for breaking software down into pieces and making software development more efficient. Many of these techniques have been sort of... and everybody got excited about but very little benefit was actually derived once the thing was put into practice.

The way to build a complex system that works is to build it from very simple systems that work.

The design of each element should be thought out in order to be easy to make and easy to repair.

At least since the Industrial Revolution, the world of design has been dominated by the rigors of manufacturing and mass production. Assembly lines have dictated a world made of parts, framing the imagination of designers and architects who have been trained to think about their objects as assemblies of discrete parts with distinct functions.

Our ultimate goal is extensible programming (EP). By this, we mean the construction of hierarchies of modules, each module adding new functionality to the system.

The whole intent of Perl 5's module system was to encourage the growth of Perl culture rather than the Perl core.

We've broken the code base into logical chunks, called modules, and the foundation staff delegate authority for the modules to people with the most expertise.

The only way to write complex software that won't fall on its face is to hold its global complexity down - to build it out of simple pieces connected by well-defined interfaces, so that most problems are local and you can have some hope of fixing or optimizing a part without breaking the whole

Oracle will continue to componentize all of its solutions so we can work in a heterogeneous environment.

The iPod is a proprietary integrated product, although that is becoming quite modular. You can download your music from Amazon as easily as you can from iTunes. You also see modularity organized around the Android operating system that is growing much faster than the iPhone. So I worry that modularity will do its work on Apple.

When you start over and jump into new tech, you don't know what the negatives are going to be until you go through a few cycles. We're always changing our tech, but we don't wholly destroy it with each game. We're taking parts out.

There is power in creating a small model, and then you can create an alliance of other small models.

Common sense steps in here and says: Separate the parts you want to be mobile from the parts you want to be inert. You have seen the result, and I know many have the skill to apply it.

The software industry has to become better in componentization. That's a clear focus for most of the software companies. How components look, how they are maintained, the ability to maintain them separately.

I don't like stuff that can only go into one set; I want stuff that can be applied across sets. It's a more real Lego building experience. And, of course, it's the same from a manufacturing point of view. I want elements that are universal; that gives me the best economics and best utilisation of the mould.