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

A Philosophy of Testing

Imagine plotting the various dimensions of your software: the functionality, performance, user interface, and so on, on a multidimensional chart (for the diagrams in this section, I'll stick to two dimensions; even if you're viewing them on some mad future reader, my graphics tool doesn't support more than that).

The first thing to notice is that you can't draw a point on Figure 6.1 that represents the "target" product to develop. The most important reason is that the target may not exist. Depending on your philosophical approach to software, there may not be a true collection of requirements that is universally understood to be the correct thing to build. Consider the people who are using the software as part of the system the software is supporting, so the "right thing" depends on those people and their interactions with each other. The thing you "should" build depends on the context and varies with time. (Manny Lehman...