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

The Teaching Of Software Creation

My mitigation for the rediscovery problem outlined above could be that you undertake the heroic effort of discovering what's out there from nearly 70 years of literature, identify the relevant parts, and synthesize a view on software creation from that. That would be crazy. But in the short term, that's probably the only route available.

Like many people, I learned programming by experimentation, and by studying books and magazines of varying quality. This means that, like many programmers, my formative experiences were not guided (or tainted, depending on your position) by a consistent theory of the pedagogy of programming. Indeed, I don't think that one exists. Programming is taught differently by professional trainers and by university departments; indeed, it's taught differently by different departments in the same university (as I discovered, when I was teaching it in one of them).

There's no consistent body of knowledge that...