How to test?" is a question that cannot be answered in general. "When to test?" however, does have a general answer: as early and as often as possible. — Bjarne Stroustrup Copy Share Image
Always think about how a piece of code should be used: good interfaces are the essence of good code. You can hide all kinds… — Bjarne Stroustrup Copy Share Image
Any verbose and tedious solution is error-prone because programmers get bored. — Bjarne Stroustrup Copy Share Image
“There are only two kinds of languages: the ones people complain about and the ones nobody uses.” — Bjarne Stroustrup Copy Share Image
Nobody should call themselves a professional if they only knew one language. — Bjarne Stroustrup Copy Share Image
It's easy to win forgiveness for being wrong; being right is what gets you into real trouble. — Bjarne Stroustrup Copy Share Image
Some software is actually pretty good, by any standard. Think of the Mars Rovers, Google, and the Human Genome Project. Now, that's quality software! — Bjarne Stroustrup Copy Share Image
C makes it easy to shoot yourself in the foot; C++ makes it harder, but when you do, it blows away your whole leg. — Bjarne Stroustrup Copy Share Image
I assume that a sufficiently skilled will be able to do anything not explicitly forbidden by the hardware. — Bjarne Stroustrup Copy Share Image
I like doing research that has an impact. If I went to a company to make what they call 'real money,' I'd be just… — Bjarne Stroustrup Copy Share Image
I would encourage nonproprietary standards for tools and libraries — Bjarne Stroustrup Copy Share Image
This evolution may compromise Java's claim of being simpler than C++, but my guess is that the effort will make Java a better language… — Bjarne Stroustrup Copy Share Image
Clearly, I reject the view that there is one way that is right for everyone and for every problem — Bjarne Stroustrup Copy Share Image
