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

Choose Appropriate Technology

As the last sentence of the previous section says, the goal here is to satisfy a business need. If that business need isn't aligned with your current favorite platform or shiny toy, you have to decide which you want to pursue. The best choice for the business – and, therefore, for your role in it as a developer – is the one that achieves the goal with least effort and fewest difficulties or compromises.

Of course, "effort" can include training – a short (and usually fixed length) effort needed to get developers and others up to speed with some new technology. But then "effort" also includes maintenance and support – ongoing costs that build up over the lifetime of the product in the field. This is sometimes ignored when estimating a project's cost, as the project ends on the ship date, so maintenance is somebody else's problem. That's a false economy though; the maintenance cost of a project...