In this first chapter, Metz makes the case that application change is unavoidable and that the best way to handle this expected volatility is through object oriented design (OOD). By following the principles and patterns of design, engineers can create malleable objects that pass meaningful messages among one another.
Below are a few questions to get our conversation started around Chapter 1. Feel free to answer any one of these and reply with a helpful comment on someone else’s post as well.
- How would you contrast procedural and object-oriented programming based on the chapter's explanation?
- Think about a project you’re currently working on. What criteria can you use to determine successful design in the next feature that you build?
- Any other thoughts or questions you have on this chapter?
Resources
