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

Don't Stick to Your Own Discipline

Every field has its champions and superheroes: the people with tens of thousands of followers, whose blog posts are always read and quoted and who speak at all the conferences. People look to these champions to analyze and direct the way their community works. Often, the leaders in one field will be contrasted with "them," the leaders in a different field: that iPhone programmer is one of "us," and the Android programmer giving a talk in the other room is talking to "them."

This definition of "us" and "them" is meaningless. It needs to be, in order to remain fluid enough that a new "them" can always be found. Looking through my little corner of history, I can see a few distinctions that have come and gone over time: Cocoa versus Carbon; CodeWarrior versus Project Builder; Mach-O versus CFM; iPhone versus Android; Windows versus Mac; UNIX versus VMS; BSD versus System V; SuSE versus Red Hat...