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

Automatically Generated Documentation

I talked in the last section about an economic trade-off associated with producing documentation: whether the cost of production is lower than the opportunity cost of not having that documentation available later. The balance can be tipped in favor of producing documentation in two ways: either by decreasing the cost of production or by increasing the value of the documentation.

The automatic generation of documentation from code—often called reverse engineering the documentation—is a tactic used to drive down the cost of production. The idea is simple: if developers can always create the docs at a moment's notice from the source code, they can always avail themselves of up-to-the-minute descriptions of how that code works.

Reverse engineering tools, which usually produce UML diagrams, a particular format of documentation discussed later in the chapter (To be clear, I'm not talking about tools that extract documentation embedded...