|
Not all traders are programmers. And not all of the programmers are really good ones. So, what should be done, if you need to automate your system by do not have time and desire to study MQL4? Usually one visits the forum and creates a topic named something like "I need a programmer":
EA programmer needed Please make Expert Advisor I need someone who can build an expert advisor for me This article is written specially for those who need help in writing an Expert Advisor. You will find here the contact information of EA-writers, recommendations on contacting them and descriptions of the most frequent problems. What Should Be Done Before Ordering an Expert Advisor? Before starting to look for a programmer, make sure that your strategy is profitable. Do not pay for an EA that will not bring profit. You can make it manually by looking through historic data or by trading mentally, which in fact is quite difficult. It can also be done using a manual tester described in the article Testing Visualization: Manual Trading. The most true results can be acquired by trading on a demo account or a mini-real account, but this requires more time and, probably, money. While testing a strategy, note that: market constantly changes and a correct behavior of indicators on history does not guarantee their being adequate in real trading; some indicators draw signals on already formed bars. Successfully placed arrows on price extremums belong to history. In real trading they will become visible only after several bars. For example, signals by Fractals are shown with a two-bar delay. You can use it, but taking into account that you will enter the market not with the fractal, but only when two more bars are formed (on an hour chart it will be in two hours). Do not use indicators, whose algorithm of operation is unknown to you. This may lead you to bad results; there are a lot of indicators, which intentionally or not look into the future. For example, the simple Moving Average with a negative shift will in due time show market pivots. But only on history... Many errors of this kind can be detected by way of testing a strategy in real-time mode on a demo-account. But this seemingly reliable check cannot guarantee a total coincidence with real trading, because demo and live accounts have some differences: speed of order execution on a demo-account is always higher than that on a live account. Be ready that you live position will be opened only in several minutes after you send an order. This won't influence results of a long-term strategy, but will fully spoil your daily trading; on a live account trade conditions (spread, distance to stop-orders, margin-call level etc.) can be change during trading. For example, prior to news releases or before holidays. While testing your strategy on a demo account, you can hardly face such surprises, but don't forget to take them into account when estimating the effectiveness of your strategy. And do not forget that real money are real money and attitude to them differs from that to a demo account. An Expert Advisor can eliminate a large part of emotions from a trading process, but it cannot fully eliminate your possible errors. Trading on a demo account, stick to one strategy, do not change your plans and do not make emotional decisions. Your future EA is only a program and it will work according to strict rules. If you want to know what results your EA can achieve, you trading style must be the same as that of an EA - concise and disciplined. If after all these checks your strategy still shows quite a good profit, enough to cover all the surprises of a real trading, you may move to the next stage - formalization of an algorithm.
Algorithm Formalization If you have been trading using your strategy long enough, it will be easy for you to formalize an algorithm. All you need is to list rules, according to which your EA should trade.
Note that the program will be written by a person that does not have the faintest idea of your strategy. You should specify all the smallest details: parameters of indicators, distance to stop-orders, maximal number of opened positions, trailing stop algorithm, etc. Your requirements specification must contain the description of the reaction on each significant event: activation of a stop-order, appearance of a repeated signal when a position exists, start of an EA after disconnection etc. You should understand that your PC cannot guess, assume or make independent decisions, - it simply trades according to our rules. If a situation occurs, the reaction on which is not provided by the algorithm, your EA will do nothing. Let us see on an example what can happen if a requirements specification is not very concise or detailed. The following dialog demonstrates the process of EA development by a Programmer according to the algorithm by a Trader. I intentionally displayed absurdly silly characters. This will emphasize the attention on errors. For a better understanding you can download examples of all EAs and test them together with the Trader. |