Agile Principles, Patterns, and Practices in C# (Robert C. Martin Series)

This led to some interesting simplifications. The system was event driven.

A war is going on among major corporations. These corporations are fighting to gain your allegiance. These corporations believe that if they own the language, they’ll own the programmers and the companies that employ those programmers.

Without changing the module, how can we change what a module does? The answer is abstraction

remember that an agile developer does not apply those principles and patterns to a big, up-front design. Rather, they are applied from iteration to iteration in an attempt to keep the code, and the design it embodies, clean.

Nobody has more authority than anybody else over a module or a technology.

One, complex hardware engineering efforts are not always as free of bugs as software critics would have us believe. Major microprocessors have been shipped with errors in their logic, bridges collapsed, dams broken, airliners fallen out of the sky, and thousands of automobiles and other consumer products have been recalled—all within recent memory

Allow no cycles in the component dependency graph.

try/catch blocks can be even uglier than checking for null. We can address these issues by using the NULL OBJECT pattern.1 This pattern often eliminates the need to check for null, and it can help to simplify the code.

“In preparing for battle I have always found that plans are useless, but planning is indispensable.”