All too often as programmers, we focus on the technical details of a program. That is, we focus on the product rather than the process of programming. The difficulties of solving a particular programming problem are so great that we forget that the problem itself will change over time. No matter how much we try to avoid it, change is inevitable: changing markets, changing requirements, and changing technologies. As programmers, we need to be able to effectively cope with this change just as much as we need to be able to implement, test, and debug our code.
Back in Chapter 4, Using Modules for Real-World Programming, we looked at an example program that faced the challenge of changing requirements. We saw how a modular design allowed us to minimize the amount of code that had to be rewritten when the scope of the program increased well beyond what was first envisaged.
Now that we have learned more about modular programming and the related technologies that can help...