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

Patterns of Software Project Management

Over the last five decades, there have been numerous different ways to run a software project proposed and practiced. Over the last decade, I've been exposed to a few of them. Which will work for you depends on the team you're working with and the expectations of the people you're working for.

Waterfall

My first experience of a "death march" was on a waterfall project. The product manager wrote a document explaining the requirements of the new product. These were prioritized using 1-3 (with 1 being "we'll probably finish these in time," and 2-3 taking up space on the page). Then, the lead developer wrote a functional specification, explaining what each of the controls in the product would be and how each of them would fulfil a requirement from the first document.

Given the functional specification, the lead developer (not necessarily the same one as mentioned previously) would estimate how long it'd take to...