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

Understand The Problem Domain

As mentioned earlier, you and your team are the experts in making software, and the customers are the experts in the thing that the software will do. I've cautioned against using that distinction to build the software you want rather than the software that the customers need; should this be taken to mean that the software people stick to software and the customers stick to their problem domain?

No.

You need to know what you're building for, so you need to have some understanding of the problem domain. Yes, this is asymmetric. That's because the situation is asymmetric – you're building the software to solve a problem; the problem hasn't been created so that you can write some software. That's just the way it is, and compromises must come more from the software makers than from the people we're working for. The better you understand the problem you're trying to solve, the more you can synthesize ideas from that domain...