Chapter 4. Organizing your work

 

This chapter covers

  • Changing at scale—small, medium, and large
  • Working alone, in a pair, or in a team
  • When to start drawing the graph
  • How to combine working with new features and structural improvements

Imagine one day you’re happily starting work on a part of the system you haven’t looked at before. You have a new requirement for the user interface that shouldn’t be too difficult to implement. But as you begin, you realize that there’s an issue with the inheritance hierarchy in one of the core components you need to use. You call in a coworker and tackle this together. Digging a bit deeper, you find that the constructor of the base component is making assumptions and calling methods that might not be ready to call in the constructor. Making matters worse, there are dependencies going back to the very initialization of the entire application. You realize that fixing this will affect a substantial part of the system.

4.1. The scope of a change

 

4.2. How to approach a change

 
 

4.3. Summary

 
 
sitemap

Unable to load book!

The book could not be loaded.

(try again in a couple of minutes)

manning.com homepage