8 Make code modular
This chapter covers
- The benefits of modular code
- Common ways code can be less modular than is ideal
- How to make code more modular
Chapter 1 discussed how requirements often evolve over the lifetime of a piece of software. In many cases they evolve even before the software is released, so it’s not uncommon to write some code and then have to adapt it only a few weeks or months later. Trying to predict exactly how requirements will evolve is usually a waste of time, because it’s near impossible to do this with any accuracy. But we can usually be more or less certain that they will evolve in some way.
One of the main aims of modularity is to create code that can be easily adapted and reconfigured, without having to know exactly ...
Get Good Code, Bad Code 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.
