Moderation in the marketplace - page 3
You are missing trading opportunities:
- Free trading apps
- Over 8,000 signals for copying
- Economic news for exploring financial markets
Registration
Log in
You agree to website policy and terms of use
If you do not have an account, please register
Do you think that in case of a bug the buyer will tell you what the problem is and in which line of code?
not here the moderator is just speaking as a future buyer.
Imagine - the buyer will buy and write in the review - "The indicator does not work, it does not draw anything".
So in this case it is worth paying attention to the indicator and the instructions ie prevent these points.
Believe me - such responses from moderators were all and everyone has learned the truth and experience.
Have you thought about what you wrote? If someone's indicator doesn't work, it doesn't mean that it doesn't work at all, it just means that either someone's hands are crooked or they haven't even bothered to read the instructions!
And how can you look for the cause in your terminal if everything is working fine! And do I have to remind the great MODERATORS to look in the log and report it to me!?
Not just report that"Indicator doesn't draw anything".
Strange reasoning: "To run the indicator -- you have to read the manual"
It is clear that when the indicator is placed on the chart, it has to draw something. Settings and instructions are of secondary importance.
Therefore, the answer of moderation: "the indicator doesn't draw" is quite correct and true.
You sell the indicator and solve your own problems.
And you have to look through your own logs. Why should moderators or buyers poke around in the seller's logs?
Test your product as thoroughly as possible.
There is a difference - the delivery of indicator to order, where there is a process of debugging - this process is natural and reasonable request to provide the logs - and there is a sale, where the buyer should not rummage in logs (at least, when the first order, it is in the process of work with very rare abnormal situation - you can ask for logs).
Strange reasoning: "To run an indicator, you have to read the instructions".
It is clear that when you put the indicator on the chart, it has to draw something. Settings and instructions are of secondary importance.
Therefore, the answer of moderation: "the indicator doesn't draw" is quite correct and true.
You sell the indicator and solve your own problems.
And you have to look through your own logs. Why the moderators or buyers should poke around in the seller's logs?
Test your product as thoroughly as possible.
There is a difference - the delivery of custom indicators, where there is a process of debugging - this process is natural and a natural request to provide the logs - and there is a sale, where the buyer should not rummage in the logs (at least, when making the first order, in the process of a very rare abnormal situation one may request logs).
Which line of code are we talking about anyway? Is the code available to the customer? Or you just came to talk? :)
Whether you have source code or not, in case of error the terminal will display not only number of line with error, but also position of error...
A buyer who knows these details can write to you that the terminal says error at line 123 and position 12, and you as the developer can get into the source code and see what error in line 123 and position 12.
The indicator doesn't necessarily have to draw something, the indicator could be drawing, converting and writing data to a file...
Have you thought about what you wrote? What am I, a psychic? If someone's indicator does not work, it does not mean that it does not work at all, it just means that either someone's hands are crooked or they didn't even bother to read the instructions!
And how can you look for the cause in your terminal if everything is working fine! And do I have to remind the great MODERATORS to look in the logbook for messages and report them to me!?
Not just to unsubscribe that"Indicator doesn't draw anything".
You better think about what you write!
If the moderator writes that it does not work then it is so, better test your ex_ on different terminals from different brokers and look at the log and expert tabs yourself.
The indicator doesn't have to draw anything, the indicator can collect, convert and write data to a file...
It should always be assumed that the end user will be the least competent and not burning with the desire to read the manuals, instructions before running the program.
If there is a sequence of actions in which there are no results of the program visible to the user (or expected), this is only a problem:
Alas, due to limited resources a lone developer is required to take on roles 2 and 3, hence all the problems are the developer's problems. Insufficient testing or insufficiently thought out system of communicating with the client is not important.
Any program must in any case at least tell the user something in the most obvious way (oh how many users do not know about the existence of logs!). Add to the code processing of all input data, all user actions, checking of all external environment, all internal states. If something is done incorrectly to the program, let it report it and at least send you to read the manual. If everything goes to fatal error ( array overruns, invalid pointer access, etc), it's clearly developer's fault, which can also be handled (by checks) and reported to user.
Moderators are not testers/representatives of the QA department, they don't have to do your work for you. After all, do you write commercial software, or ...? :)
Of course, this is all just my opinion and you can not disagree with it.
Strange reasoning: "To run an indicator, you have to read the instructions".
It is clear that when you put the indicator on the chart, it has to draw something. Settings and instructions are of secondary importance.
Therefore, the answer of moderation: "the indicator doesn't draw" is quite correct and true.
You sell the indicator and solve your own problems.
And you have to look through your own logs. Why the moderators or buyers should poke around in the seller's logs?
Test your product as thoroughly as possible.
There is a difference - the delivery of indicator on demand, where there is a process of debugging - this process is natural and reasonable request to provide the logs - and there is a sale, where the buyer should not rummage in the logs (at least, when the first order, it is in the process of work on a very rare abnormal situation you can ask for the logs).
Why this strange reasoning? One and the same indicator may be interpreted by each user differently - "to" or "from", on a "bounce" or "breakout", etc.
Or do you think that the buyer pays money for a picture of the indicator without even going into the essence of what is written?
The indicator did not show up on the chart, but "drew" a message in the log that certain quotes were missing, which the moderator did not even bother to pay attention to!
At least it was written in black and white in the instruction, verbatim: "Make sure that all 28 currency pairs containing 8 currencies (USD, EUR, GBP, CHF, CAD, AUD, NZD, JPY) are present in the Market Watch window".
I think the answer "the indicator doesn't draw" is useless, uninformative and not correct! I, like everyone here, am not a psychic!