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

Application of The Ethical Code

Abiding by some code of ethics is more expensive than ignoring it. The ACM code tells us to "Honor property rights including copyrights and patent": obviously, it's cheaper to steal someone else's copyrighted work than to build an equivalent work. Examples could be found for the other moral imperatives in the code.

Legal systems work, broadly speaking, by introducing a cost of non-compliance so that rational actors should also be abiding actors. This is an example of removing an externality, discussed in Chapter 15, Philosophy, of this book. If stealing the copyrighted work is going to cost the thief in legal fees, damages, and lost reputation, the other route becomes attractive.

For most of us making software, the legal framework we operate in doesn't directly apply to our actions. Laws exist covering data protection, and certain fields are strongly regulated (principally, life-critical systems such as control software for medical devices...