108 Quotes by Robert C. Martin

The cost of automating acceptance tests is so small in comparison to the cost of executing manual test plans that it makes no economic sense to write scripts for humans to execute.

If a test in the same package needs to call a function or access a variable, we’ll make it protected or package scope.

In fact, wrapping third-party APIs is a best practice. When you wrap a third-party API, you minimize your dependencies upon it:.

For example, class names including weasel words like Processor or Manager or Super often hint at unfortunate aggregation of responsibilities.

Factories are a complexity that can often be avoided, especially in the early phases of an evolving design.

Consider, for example, the truly hideous practice of creating a variable named klass just because the name class was used for something else.

Complexity kills. It sucks the life out of developers, it makes products difficult to plan, build, and test.” – Ray Ozzie, CTO, Microsoft Corporation.

Perhaps you thought that “getting it working” was the first order of business for a professional developer. I hope by now, however, that this book has disabused you of that idea. The functionality that you create today has a good chance of changing in the next release, but the readability of your code will have a profound effect on all the changes that will ever be made.

The problem that Dijkstra recognized, early on, was that programming is hard, and that programmers don’t do it very well.