System Development Quotes

Physicists analyze systems. Web scientists, however, can create the systems.

When I launched the development of the GNU system, I explicitly said the purpose of developing this system is so we can use our computers and have freedom, thus if you use some other free system instead but you have freedom, then it's a success. It's not popularity for our code but it's success for our goal.

Conceptual integrity is the most important consideration in system design.

The visible things that have come from the group have been the Plan 9 system and Inferno, but I hasten to say that the ideas and the work have come from colleagues.

In any software work, you have IT consultancy competence required to build the systems.

If you look at the minutes of the constitutional convention - which we have - Madison who was the main framer, proceeded to develop a system in which - as he put it - power would be in the hands of the wealth of the nation, the more responsible set of men and who recognize the need to protect the rights of property owners. That's why in the constitutional system, the most powerful part of the whole system is the senate.

The designer of a new kind of system must participate fully in the implementation.

And what I learned in Church's course. He trained us intensively in his new system, which he was just developing. Two papers were presented. I think the second paper wasn't published until well after the course was finished.

People work in the system. Management creates the system

What I like about the USTA is that it's developing systems to help the coaches coach better.

People who get Nobel prizes aren't necessarily the most imaginative of people. People who sometimes find a system, develop a system, do very useful work.

Management works in the system; leadership works on the system.

The belief that complex systems require armies of designers and programmers is wrong. A system that is not understood in its entirety, or at least to a significant degree of detail by a single individual, should probably not be built.

There is no one "root of all evil" in software development. Design is hard in many ways. People tend to underestimate the intellectual and practical difficulties involved in building a significant system involving software. It is not and will not be reduced to a simple mechanical "assembly line" process. Creativity, engineering principles, and evolutionary change are needed to create a satisfactory large system.

The system is only as good as the person programming it. If you don't have the follow-through, your system is useless. And by the way, it's that way in parenting; it's that way in marriages.

I took what worked for me and found I had a system that others were interested in and seemed to work for a wide number of people. It was recognised by other martial artists, grandmasters and such, and they gave me the recognition. I'm proud of my work in martial arts. I still teach but only once a week in a private class, and I train a couple more days a week.

If you sense a deep human need, then you go back to all the basic science. If there is some missing, then you try to do more basic science and applied science until you get it. So you make the system to fulfill that need, rather than starting the other way around, where you have something and wonder what to do with it.

There are more useful systems developed in languages deemed awful than in languages praised for being beautiful - many more.