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

Forms Of Fallacy

This section takes the form of a catalog, of sorts. It's not going to be complete and won't take a formal approach to describing the catalog in the same way that, for example, Design Patterns deals with its catalogue; a complete catalogue of fallacies would be at least as long as the rest of this book. A formal and consistent catalog would require planning.

Post Hoc, Ergo Propter Hoc

Translated, this means "After this, therefore because of this." Given two events, X and Y, the argument goes:

First X, then Y. Y was therefore caused by X.

This is a form of inductive reasoning that does not necessarily hold. Here's an absurd example:

The light turned red, and the car came to a halt. Red photons exert a strong retarding effect on cars.

In this case, there could be a causative relationship, but it is not as direct as the argument proposes.

Fundamental Attribution Error

Person P did X. Therefore, P is a moron.

This is also called correspondence bias. People often...