In my opinion, writing good software is less like writing (the analogy of copy-and-paste holds to coding as well as writing) and more like weaving. Writing, at least, in the chapter format, isn't tightly coupled in terms of chapters as program modules. Yes, most books have an overarching plot - but how many programs are stories? They are more like buildings. The infrastructure (HVAC, electrical) must be in place before building floors. Floors can vary and be isolated. The building as a whole serves a business purpose. Oh and make sure your critical infrastructure cannot be flooded (Sandy). Tiny Towers - FTW!

With weaving, you have to be attuned as the whole structure of the cloth before you start writing. You need to see the big picture and concentrate on the details.

Yes, there is no equivalent refactoring tool like an IDE for weaving but I belabor my point..