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

What You Discover May Not Be to Your Liking

Sometimes, you'll look at the results of the research you've done and realize that things don't look promising.

Perhaps there aren't as many customers for your product as you first assumed, development is going to be harder, or you've found a competing product you didn't know about before. Perhaps the task you estimated would take 2 days is going to take longer than a week.

You need to decide what you're going to do about that. The worst way to do this is by ignoring the problem: you're relying on luck or on faith to get you through. You're cleverer than that; you can think of a plan to overcome the problem.

Personal Experience

One of the first software projects I worked on had a team of three developers, none of whom had much experience with the technology we were using, and two of whom (myself included) didn't really have much experience of anything.

As we progressed with the project, we found that...