Bjarne Stroustrup Quotes

Another trick in software is to avoid rewriting the software by using a piece that's already been written, so called component approach which the latest term for this in the most advanced form is what's called Object Oriented Programming.

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

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.

Object-oriented design is the roman numerals of computing.

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.

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

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.

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

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.

Clearly, programming courses should teach methods of design and construction, and the selected examples should be such that a gradual development can be nicely demonstrated.

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

Progress is possible only if we train ourselves to think about programs without thinking of them as pieces of executable code.

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

If you want to go somewhere, goto is the best way to get there.

If 10 years from now, when you are doing something quick and dirty, you suddenly visualize that I am looking over your shoulders and say to yourself: 'Dijkstra would not have liked this', well that would be enough immortality for me.

First you learn the value of abstraction, then you learn the cost of abstraction, then you're ready to engineer.

No one wants one language. There are applications when it's appropriate to write something in C rather than in Java. If you want to write something where performance is much more important than extensibility, then you might want to choose C rather than Java.

It is easy to study the rules of overloading and of templates without noticing that together they are one of the keys to elegant and efficient type-safe containers.

If you're talking about Java in particular, Python is about the best fit you can get amongst all the other languages. Yet the funny thing is, from a language point of view, JavaScript has a lot in common with Python, but it is sort of a restricted subset.

A programming language is low level when its programs require attention to the irrelevant.

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

The fact that the same symbolic programming primitives work for those as work for math kinds of things, I think, really validates the idea of symbolic programming being something pretty general.

It's very hard to explain to people who don't program, but the object-oriented programming system made programming the Mac and iPhone so easy.