Bill Gates Quotes

Defining OO as based on the use of class hierarchies and virtual functions is also practical in that it provides some guidance as to where OO is likely to be successful.

Object-oriented programming is an exceptionally bad idea which could only have originated in California.

I made up the term "object-oriented," and I can tell you I did not have C++ in mind.

Certainly not every good program is object-oriented, and not every object-oriented program is good.

Nevertheless, I consider OOP as an aspect of programming in the large; that is, as an aspect that logically follows programming in the small and requires sound knowledge of procedural programming.

Object-oriented programming as it emerged in Simula 67 allows software structure to be based on real-world structures, and gives programmers a powerful way to simplify the design and construction of complex programs.

Object-oriented design is the roman numerals of computing.

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.

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

When you're working with an object, you can put in almost anything you want, you can make it abstract.

Perhaps the central problem we face in all of computer science is how we are to get to the situation where we build on top of the work of others rather than redoing so much of it in a trivially different way.

I used to be enamored of object-oriented programming. I'm now finding myself leaning toward believing that it is a plot designed to destroy joy.

When there is no type hierarchy you don't have to manage the type hierarchy.

If you have a procedure with 10 parameters, you probably missed some.

Adding functionality is not just a matter of adding code.

No matter what, the way to learn to program is to write code and rewrite it and see it used and rewrite again. Reading other people's code is invaluable as well.

My favorite language for maintainability is Python. It has simple, clean syntax, object encapsulation, good library support, and optional named parameters.

Lisp isn't a language, it's a building material.

I will, in fact, claim that the difference between a bad programmer and a good one is whether he considers his code or his data structures more important. Bad programmers worry about the code. Good programmers worry about data structures and their relationships.

There's only one trick in software, and that is using a piece of software that's already been written.

The art of programming is the art of organizing complexity.

Java and C++ make you think that the new ideas are like the old ones. Java is the most distressing thing to hit computing since MS-DOS.

Good programmers know what to write. Great ones know what to rewrite (and reuse)

Copying all or parts of a program is as natural to a programmer as breathing, and as productive. It ought to be as free.