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

Automate All The Things

Testing software and writing software share the following property in common: it's not doing them that's beneficial, it's having done them. Having access to finished, working software is a useful thing, so a project that's in progress is only as valuable as one that hasn't started (although the in-progress one has already cost more). Therefore, as much of the testing procedure itself should be automated as possible to let testers get on with the more creative tasks of defining tests and discovering/reporting issues.

This automation starts with setting up the test environment into a known, initial state. Virtual machines are increasingly being used for this task (at least in server and desktop environments) because they offer a quick way to create an environment of known configuration into which the test harness and the software it's testing can be deployed. At the end of a test run, the state of the virtual machine is reset and it&apos...