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

Conclusion

I wrote this book to reflect on what I knew about making software and to understand what I didn't know about making software. I published it so that you could take advantage of what I've found over the decade I've been doing this for a living, and to trigger your own reflections on your experiences (with the hope that you would share these with us, just as I have).

I started by looking at the things we do when we're at the coal face: the tools and practices we use to convert ideas into software. Then I looked at how we work with other people: how we document what we've done; how we find out what software needs writing; how we take advantage of opportunities to learn from other people, interpret other people's arguments, and work with them in the context of a team or a business. Finally, I tried to construct a high-level model in which to situate all of that work, by considering the ethics and philosophy of making software, and how to move our knowledge...