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

Working with Managers

There are two (almost opposing) interpretations of the word "manager" as it applies to the work context. The conservative view is of the manager as the controlling force in charge of a group of people. This manager's position is seen as ensuring that their reports do the work expected by the business, and by extension, don't do anything unexpected.

The liberal view is the manager as leader or enabler. This manager's role is to ensure that their reports have the resources they need to get their work done, free from distractions that the rest of the business (or its customers and suppliers, and so on) might impose.

In this section, I'm going to leave the political models aside and discuss the general idea of working with the person you have to report to. If you're a self-employed programmer, you don't have an explicit manager. You may still find, from time to time, that certain people fill similar roles; I know some independent developers...