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

You Shouldn't Necessarily Build What The Client Asks For

Discovering the requirements for any software application is hard, even if the people building it are going to be the people using it. In Chapter 6, Testing, I explored the notion that everybody has their own idea of what the software should do, and in Chapter 7, Architecture, the fact that some requirements are not made explicit. So, if you just asked everyone for a list of things the software should do and built that, it'd be rife with conflicts and probably wouldn't do everything that any one person wanted from it.

While it's an inaccurate way of finding out what software should do, asking people is one of the easiest and most accessible methods. You can interview people with either a directed questionnaire or an open-ended discussion, finding out what they think of the system of interest and hopefully teasing out some of those tacit requirements. You can also get a group of people together, as a round-table discussion...