Summary

In this chapter, we demonstrated the following points:

  • Refactoring allows the design of the code to improve by following a series of simple steps. For example, in this chapter we went from bad procedural code to a cleaner object-oriented implementation—while staying close to the green bar and without a large-scale rewrite. When you write your code, we expect you will refactor as you discover the need for it (not when it’s too late and the code is so messed-up that it is more appealing just to throw it away and write it anew). The more "paranoid" you are about all the little problems in the code, the more proactive you will be in correcting them when you notice them rather than waiting until you have a big job on your hands.

  • There was no ...

Get Test-Driven Development in Microsoft® .NET now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.