Self-learning the MQL5 language from scratch - page 20

 
Vasiliy Sokolov:

Decomposition... - You do one task and solve all at once. That's the point.

It is more of a universalization. Decomposition is the parsing of internal content. Which shelves and in what order is the second question. After decomposition of a set of similar objects, the approach to their processing is generalized (universalized). It is the stage following the multiple composition of similar objects.
 
Реter Konow:
What if striving for creative freedom gets in the way?) What if the "I" stands in opposition to the "they" and that's where the inspiration comes from?) Give up and become "one of" instead of "one"?

In order to create, you must first get the necessary set of knowledge: repetition - mistake - stick - repetition again - success - biscuit and so on several times.

Children, for example, are all such creative individuals. And everyone is so 'special', but for some reason there are paintings by adults in galleries, and we don't read books written by children either.

 
Vasiliy Sokolov:

Yes, decomposition is quite a concrete set of steps: "Do one, do two, do three". It's almost an exact algorithm. So precise, for example, that Resharper can do many things from decomposition. The only reason it doesn't do everything is because everyone's needs are different, there's no common basis for it.

Well, the MT EA code generator automatically builds it too. Can we say that it has decomposed the topic of algotrading and therefore copes with this task? The developers have done it for him by generalising some of the content types of the simplest EAs.
 
Реter Konow:
Well, MT's EA code generator automatically builds it too. Can we say that it has decomposed the topic of algotrading and therefore handles the task so well? The developers have done it for him by generalizing some of the content types of simple Expert Advisors.

code generation != decomposition

 
Vasiliy Sokolov:

In order to create, you must first get the necessary set of knowledge: repetition - mistake - stick - repetition again - success - biscuit and so on several times.

Children, for example, are all such creative individuals. And everyone is so "special", but for some reason there are adult paintings in galleries, and we do not read books written by children.

Yes, I see.) I meant it as a joke.

And yet, decomposition is a physical/intuitive dissection of an object/apparition into its parameters, connections, and functions, in order to study/reproduce it. The synthesized instance may have the same forms and mechanisms as the original, but a fundamentally different content/idea behind it. This approach enriches both the view of the object itself and its implementation. Uniformity in decomposition, composition, universalisation and so on is a dead end in development.

In general, any prolonged monotony is a dead end.
 
Vasiliy Sokolov:

Decomposition is all about optimisation and code solving. These are not second and third tasks. This is decomposition. And creating logic is also decomposition. Everything is decomposition. You do one task and solve all at once. That is the point.

It is not always possible to build correctly at once, especially on tasks being implemented for the first time)))) So yes, it's better to get it right at once))))))

 

So, Konov comes along and makes a mess out of a generally useful topic.

 
Maxim Kuznetsov:

So Konov came along and made a rubbish dump out of a generally useful topic.

Wipe your rubbish comment from here.
 
Реter Konow:
Erase your rubbish comment from here.

Kill yours... Get philosophical in your own threads.

People here are trying to help newbies for once.

 
Maxim Kuznetsov:

Kill yours... Get philosophical in your own threads.

People here are trying to help newbies for once.

Disappear with your "Konov came..." complaints.