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

Behavior-Driven Development

I found it hard to decide whether to put BDD in this chapter or to discuss it with teamwork, because it's really an exercise in communication masquerading as a coding practice. But it's here, so there you go. Indeed, many of the sections in this chapter will skirt that boundary between coding and communication, because programming is a collaborative activity.

BDD is really an amalgamation of other techniques. It relies heavily on DDD ideas like the ubiquitous language and combines them with test-driven development. The main innovation is applying test-first principles at the feature level. Using the ubiquitous language as a Domain-Specific Language (http://martinfowler.com/books/dsl.html), the team works with the customer to express the specifications for features in an executable form, as an automated acceptance test. Then, the developers work to satisfy the conditions expressed in the acceptance tests.

My own experience has been that BDD tends to stay...