Discussion of article "How to Order an Expert Advisor and Obtain the Desired Result"

 

New article How to Order an Expert Advisor and Obtain the Desired Result is published:

How to write correctly the Requirement Specifications? What should and should not be expected from a programmer when ordering an Expert Advisor or an indicator? How to keep a dialog, what moments to pay special attention to? This article gives the answers to these, as well as to many other questions, which often don't seem obvious to many people.

Author: Andrey Khatimlianskii

 

After reading the article, TK to burn. :)

Good article, Andrei. Much more extensive than the last one.

In general, the article is good for PR of professional programmers so that customers know what functions of libraries they buy. In fact, a programmer just resells his ready-made codes. He only changes the input conditions or the places where conditions are decoupled for a particular TOR.
Two-year-old "grandfathers" have their own developments and principles of code construction, and they just resell them to each new customer.

My opinion is that tapping yourself in the chest that here I am such a cool programmer added to your code normalisation of price and lot - already looks unprofessional, to put it mildly. All these functions and checks should be in the code by default, it should not even be negotiated with the customer!
They just have to be there.

That's why it is better to read the article under the title "What should be in the arsenal of a custom programmer".

And if I were the customer , I would ask the executors - have you read this article from 5.3 to 9 sections? Do your libraries take into account everything described in it? And if not, I would not even address such a programmer. Let him sit and learn the matrix, or write experts to make his own bumps.

 

According to the history of using the past article (when almost all programmers referred to it) in this article, please add:

- points/thesis of the main ideas, like an outline of the article in the beginning (as it was done in the last article)

so that you could "send" to a specific place on the link at once, instead of asking to search and read everything.

 
sergeev:

so that you can "send" to a specific place at once.

)
 
+10
 
The article is very good and useful. The author is very good.
 
sergeev:

After reading the article, TK to burn. :)

Good article, Andrei. Much more extensive than the last one.

In general, the article is good for PR of professional programmers so that customers know what functions of libraries they buy. In fact, a programmer just resells his ready-made codes. He only changes the input conditions or the places where conditions are decoupled for a particular TOR.
Two-year old "grandfathers" have their own developments and principles of code construction, and they just resell them to each new customer.

My opinion is that tapping yourself in the chest that here I am such a cool programmer added to your code normalisation of price and lot - already looks unprofessional, to put it mildly. All these functions and checks should be in the code by default, it should not even be negotiated with the customer!
They just have to be there.

That's why it is better to read the article under the title "What should be in the arsenal of a custom programmer".

And if I were the customer , I would ask the executors - have you read this article from 5.3 to 9 sections? Do your libraries take into account everything described in it? And if not, I would not even address such a programmer. Let him sit and learn the matrix, or build experts to fill his own bumps.

The idea of reselling "your ready-made codes" is correct. But I would specify that a programmer resells a cut-down ready code. And the degree of trimming depends on the cost of the order. After all, the programmer gives the source code of his universal framework. It's like "ribs", the more they pay, the more meat. It's just that the "two-year grandfather" has a universal framework debugged and fewer errors.

The principal classification of complexity and richness of software development in point 3 of the article is extremely important. And it is this classification that defines the "default" set of functions.

 
abolk:

The idea of reselling "your own ready-made codes" is a good one.

yep, try to visit a car repair shop, see how the master repairs the car with his own tools and declare that if you had such tools, you would fix it yourself even better - the best thing that awaits you is a "solemn handing over of a spanner" with the words - fix it yourself, clear the garage in 30 minutes ;)

no resale, no winged phrases like this part of the code was stolen from I.Kim, etc. - there is a task, there is a person who processed a huge pile of other people's and his own codes and fulfilled the task, a programmer gets money not for "stomping on the keyboard", but for his time already spent on learning the art of programming and preparing his tools.

thank you very much to the author of the article, he explained quite well and most importantly clearly who and what he should be able to do.

 
IgorM:

Yeah, try to go to a car repair shop, see how the master repairs the car with his tools and declare that if you had such tools, you would fix it yourself even better - the best thing that awaits you is a "solemn handing over of a spanner" with the words - fix it yourself, make the garage free in 30 minutes ;).

Well, firstly, who said that selling finished products is bad? It is natural and normal. I think you will agree that you have not created the know-how of a forex product.

Secondly, when someone comes to a car service (or comes to a dentist), of course he realises that the specialist will do his job much faster than he does. This (time, knowledge) is what he pays for.

A programmer gets money not for "stomping on the keyboard", but for his time already spent on learning the art of programming and preparing his tools.

that's what we're talking about.

 
IgorM:

Yeah, try to go to a car repair shop, see how the master repairs the car with his tools and declare that if you had such tools, you would fix it yourself even better - the best thing that awaits you is a "solemn handing over of a spanner" with the words - fix it yourself, the garage in 30 minutes free ;)

no resale, no winged phrases like this part of the code was stolen from I.Kim , etc. - there is a task, there is a person who processed a huge pile of other people's and his own codes and fulfilled the task, a programmer gets money not for "stomping the keyboard", but for his time already spent on learning the art of programming and preparing his tools.

thank you very much to the author of the article, he explained quite well and most importantly clearly who and what he should be able to do.

What are you talking about? "To him - about Thomas, and he - about Erma". Do you think that 90% of Expert Advisors that work off indicator(s) signals, accompanying an open position(s) and then closing it(s) have each unique algorithm? And that the expert writer writes each code anew "from scratch". Or maybe the programmer takes his already ready and debugged Expert Advisor from another, similar task, makes the necessary adjustments and gives it to the customer.

Or do you think that there will be one customer who will pay you for your years of "stomping the keyboard"? That's why orders for standard tasks are inexpensive, because the programmer, as it was already said, "resells ready-made codes", thus recouping his costs code by code.

 
abolk:

What are you talking about? "To him - about Thomas, and he - about Erma". Do you think that 90% of Expert Advisors that work off indicator(s) signals, follow the open position(s) and then close it(s) have a unique algorithm? And that the expert writer writes each code anew "from scratch". Or maybe the programmer takes his already ready and debugged Expert Advisor from another, similar task, makes the necessary adjustments and gives it to the customer.

Or do you think that there will be one customer who will pay you for your years of "stomping the keyboard"? That's why orders for standard tasks are inexpensive, because the programmer, as it was already said, "resells ready-made codes", thus recouping his costs code by code.

I completely agree with abolk, many programmers have written ready blocks of simple algorithms from which you then assemble an Expert Advisor like a lego constructor. I also do this. It allows you to avoid many errors when writing code in one heap.