Bjarne Stroustrup Quotes

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.

In programming, as in everything else, to be in error is to be reborn.

Developers, developers, developers...

Developers, developers, developers, developers.

We're systems software people ourselves. We wanted a language to make our lives better.

Adding functionality is not just a matter of adding code.

Low-level programming is good for the programmer's soul.

And, I think that is actually appropriate because I'm really not the world's best programmer, I think it's a good thing that I'm not touching the code.

One of my most productive days was throwing away 1,000 lines of code.

Most of the effort in the software business goes into the maintenance of code that already exists.

The second stream of material that is going to come out of this project is a programming environment and a set of programming tools where we really want to focus again on the needs of the newbie. This environment is going to have to be extremely user-friendly.

Programmers can be lazy.

APL is a mistake, carried through to perfection. It is the language of the future for the programming techniques of the past: it creates a new generation of coding bums.

So Chuck and I looked at that and we hacked on em for a while, and eventually we ripped the stuff out of em and put some of it into what was then called en, which was really ed with some em features.

Any good software engineer will tell you that a compiler and an interpreter are interchangeable.

An individual developer like me cares about writing the new code and making it as interesting and efficient as possible. But very few people want to do the testing.

I knew tech was going to be increasingly important in my lifetime, so I focused on it early.

In my daily work, I work on very large, complex, distributed systems built out of many Python modules and packages. The focus is very similar to what you find, for example, in Java and, in general, in systems programming languages.

I basically wrote the code and the specs and documentation for how the client and server talked to each other.

Computer programming is pretty much guaranteed income. I'm good at it, and I like it.

The mark of a mature programmer is willingness to throw out code you spent time on when you realize it's pointless.

I love computer programmers. They have a very beautiful definition of complexity as 'the capacity to transmit the maximum information with the minimum data'.

In software engineering, we have the term 'technical debt.' When you don't do a job correctly, unaddressed problems become harder and harder to solve.

Some of these isolated applications that sit on one machine are a million lines of code. How do you deal with that? Most people have no way to wrap their head around it.

I don't like programming. It's tedious.