Object-oriented thinking

Hello. In this post, we would like to know the opinion of the Habra-society, whether a translation book on object-oriented concepts is needed. The theme of the book is interesting, but how much is it in demand with us?
Book on amazon.com
The first chapter in the original .

Content:
1. Introduction to object-oriented concepts
2. How to learn to think in object categories
3. Advanced Object Oriented Concepts
4. The structure of the class
5. Grading Design Guide
6. Design using objects
7. Mastering Inheritance and Composition
8. Framework and reuse: designing with the use of interfaces and abstract classes
9. Building objects and object-oriented design
10. Creating object models
11. Objects and portable data: XML and JSON
12. Stored objects: serialization, marshaling and relational databases
13. Objects in web services, mobile and hybrid applications
14. Objects and client / server applications
15. Design patterns

What is this book about

As the name implies, the book talks about object-oriented (OO) thinking. Of course, it is very important to choose a theme for the book and correctly title it, but this task turns out to be difficult if the theme of the book is very conceptual. Many books are devoted only to one or another level of programming, such as object-oriented analysis, object-oriented design, object-oriented programming, design patterns, object-oriented data (XML), unified modeling language (UML), object-oriented web development , object-oriented mobile development, various object-oriented programming languages ​​and many other topics related to object orientation.
')
However, when studying all these books, many people forget that all these diverse topics are built on one basic concept: object-oriented thinking. Often, both professional programmers and students embark on the study of such books, without bothering to first understand the design concepts underlying the code.

I dare say that the study of object-oriented concepts is not limited to the study of a specific development method, programming language or set of design tools. An object-oriented approach to work is, in essence, a way of thinking. It is about object-oriented thinking and tells this book.

The target audience

This book is a general introduction to fundamental object-oriented concepts. All theoretical calculations are supported by code examples. One of the most difficult tasks was to simultaneously ensure the conceptuality of the entire code and form a solid code base. The purpose of this book is to help the reader understand concepts and technology without directly referring to the compiler. If you are going to work with the compiler, then the code from the book should be executed and examined.

The target audience of this book includes managers, designers, developers, programmers, project managers, as well as all other readers who want to get a general idea of ​​object orientation. After studying this book, you will gain good basic knowledge that will help you when reading other books on topics related to object orientation.

How is this book built

So, I am deeply convinced that you first need to master the process of object-oriented thinking, and only then proceed to the study of a specific programming language or modeling. This book contains many code examples and UML diagrams. However, you can start reading a book without knowing a particular object-oriented language or UML. But if I have already said so much about concepts, then why is there so much Java, C # .NET, VB .NET, and Objective-C code in the book, as well as so many UML diagrams? First, they illustrate the story well. Secondly, such examples are very important for understanding object orientation and should be considered already at a basic level. I don’t want to elaborate on Java, C # .NET, VB .NET, Objective-C, or UML, but I want to use them as a material illustrating basic concepts.

Also note that I use UML class diagrams specifically as illustrations to study classes, their attributes and methods. In fact, class diagrams are the only UML component covered in this book. I believe such diagrams are great for representing the conceptual nature of object models. In the future, I continue to use object models as a visual aid in explaining the structure of classes and their relationships.

In examples of the code to this book, in particular, such entities as cycles and functions are described. But to understand these concepts it is not necessary to understand the code itself in detail. If you are interested in details, it is better to have a book on hand that tells you about the syntax of a particular language.

Once again, this book does not teach Java, C # .NET, VB .NET, Objective-C, or UML — there is already extensive literature on all these topics. I hope that my book will arouse your interest in other aspects of object orientation: analysis, design and, of course, programming.