When to start learning data oriented programming

[Peter Schuster]

Hello Yehonathan!

I am quite new to learning design patterns. Since your book is addressed to experienced programmers, is it too early for me to start reading about data oriented programming, to have a benefit?

Thank you!

Peter

[Randy Tong]

I will suggest you to have basic knowledge about the fundamentals and syntax of relevant programming language before moving forward for learning OOP's concept.

[Sean Corfield]

Randy Tong wrote:before moving forward for learning OOP's concept.

Did you mean data oriented programming there Randy?

[Frank Carver]

Consider the following terms:

Object-Oriented programming

Data-Oriented programming

Procedural programming

Structured programming

Modular programming

Functional programming

The important word in all of these terms is "programming". All of these approaches (and many more) are primarily mental tools which give you different ways of looking at problems and potential solutions. For any of them to make sense you first need to have a feel for the basics of programming such as performing one thing after another, making decisions, storing values for use later and so on.

You can apply these mental tools in pretty much any programming language, but none of them is a one-size-fits-all answer. Almost all real software systems will consist of a combination of approaches. Some parts of a system may be more suitable to a data-oriented approach, some parts may be more suitable to a functional or object-oriented approach. Without experience of trying several different approaches you are unlikely to be able to choose the most appropriate techniques.

In short: pick a programming language and start solving problems. Learn from your experience. Don't be afraid to try new things. Then come back and look again at these kinds of terms.
You may find you have been doing some of them anyway!

[Yehonathan Sharvit]

I think that once you have a little experience with programming, you will find the book interesting.
The main goal of the book is to teach OOP developers how to reduce the complexity of the systems they build and maitain.