Total time (including the completion of the exercises): 50 minutes.
Good that it ends with a series of exercises that puts the reader in front of the IDE.

Overall, the chapter was a bit of a crash introduction. The book makes a brief reference to analysis and design and accurately indicates that these are the most important steps in the development of an application…Curiously, however, neither one of the traditional program planning methodologies – psudeocode or flowcharts – are mentioned. Ironically there’s even a flowchart to illustrate the development process.

I think those of us in the technical world have deliberately invented obscure terms to hide the simplicity of what we actually do. This chapter is no exception:

• Encapsulation. A more intuitive term would be “compartmentalization.” Basically, in object oriented programming, we create “objects” that contain data and do stuff to data and other objects. But encapsulation, I imagine, sounds much more mysterious to non technical folks (and thus, justifies the amount of money programmers are paid).
• Inheritance. Like as in money? No. This aspect of object oriented programming allows you to take the data and procedures of one object and add data and procedures to create a new or “extended” object of your own creation. The idea is that if functionality already exists, you shouldn’t have to re-invent it.
• And my personal favorite: Polymorphism! A two bit buzz word that means you can pass different data to a procedure and have it handle that data correctly.

These attributes are important but I think that the gratuitous use of technical jargon is really just a cover up.