Book Image

Modern Programming: Object Oriented Programming and Best Practices

By : Graham Lee
Book Image

Modern Programming: Object Oriented Programming and Best Practices

By: Graham Lee

Overview of this book

Your experience and knowledge always influence the approach you take and the tools you use to write your programs. With a sound understanding of how to approach your goal and what software paradigms to use, you can create high-performing applications quickly and efficiently. In this two-part book, you’ll discover the untapped features of object-oriented programming and use it with other software tools to code fast and efficient applications. The first part of the book begins with a discussion on how OOP is used today and moves on to analyze the ideas and problems that OOP doesn’t address. It continues by deconstructing the complexity of OOP, showing you its fundamentally simple core. You’ll see that, by using the distinctive elements of OOP, you can learn to build your applications more easily. The next part of this book talks about acquiring the skills to become a better programmer. You’ll get an overview of how various tools, such as version control and build management, help make your life easier. This book also discusses the pros and cons of other programming paradigms, such as aspect-oriented programming and functional programming, and helps to select the correct approach for your projects. It ends by talking about the philosophy behind designing software and what it means to be a "good" developer. By the end of this two-part book, you will have learned that OOP is not always complex, and you will know how you can evolve into a better programmer by learning about ethics, teamwork, and documentation.
Table of Contents (18 chapters)
Free Chapter
1
Part One – OOP The Easy Way
5
Part Two – APPropriate Behavior

Objects Are Independent Programs

The easiest problem to solve is allowing developers to independently design objects without expressing constraints that inhibit the developers' design freedoms. One way is to provide a MetaObject protocol that allows developers to adapt the rules of a language to fit a particular context. An even easier way (both to create and to use) is to make the primitive parts of the message system available to developers, to combine as needed to fulfill their design goals.

This is easier to create because any more complex system would need these primitives anyway. It is easier to use because it allows the developers to construct solutions to problems as they encounter them, rather than trying to work out how to adapt existing rules onto the models they have for their solutions. That adaptation was one of the difficulties with using OOP we explored in Chapter 1, Antithesis: if what you've got is Java inheritance, you need to solve your problem using Java inheritance...