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

Bug and work tracking

For most of their history, computers have excelled at doing things one at a time. Even a single client or customer can parallelize much better than that and will think of (and make) multiple requests while you're still working on one thing.

It's really useful to write all of these requests down, and keep track of where you and your colleagues are on each of them so that you don't all try to solve the same problem, and can let the client know which of them you've fixed. Bug trackers (sometimes more generally called issue trackers or work trackers) are designed to solve that problem.

What Goes in And When?

I've worked on projects where the bug tracker gets populated with all of the project's feature requests at the beginning (this discussion overlaps slightly with the treatment of software project management patterns, in Chapter 13, Teamwork). This introduces a couple of problems. One is that the Big List needs a lot of grooming and editing...