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

Ethical Ambiguities

It's always easier to model the world as a system of exclusive choices: this is good, that is bad; this is right, that is wrong; this is fast, that is slow. Unfortunately, such a model can quickly be found to have too many limitations. Different ethical principles all-too-readily come into conflict. Part of our responsibility as members of society is to identify and resolve these conflicts (after all, if ethics were a simple application of rules, we would've got a computer to do it by now).

Let me provide an example from my own experience. I was offering advice to another programmer about applying and interviewing for new jobs, when this person told me about an interview they had attended. They described feeling that the interview had been discriminatory on the basis of candidates' ethnicities, which is clearly in breach of any professional ethics system. Referring to the ACM's code, this breaks imperative 1.4: Be fair and take action not to discriminate...