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

Defer When Appropriate; Commit When Necessary

Working with successively refined prototypes means that the architecture becomes iteratively more complete; therefore, certain decisions become more "baked in" and difficult to change. Remember the notion presented earlier: that the architecture should always be ready to answer developer questions. This means that whatever the developers work on first are the things that should be solved first. But that's a tautological statement, because you can probably arrange the development work to track the architectural changes.

The best things to start with are the riskiest things. They might be the exploratory aspects of the product that aren't similar to anything the team has worked on before, they could be the parts that interface with other software or other organizations, or they could be the aspects that will potentially have the highest cost. These are the aspects of the application that will most likely change, and where change...