Most people must be familiar with the phrases Trade Robot, Bot Trade, Expert Advisor, or 1001 other beautiful names.

So what are these things essentially?

When it comes to Robots, Bots, many people often imagine super big, super cool, super cool things, ... (The size of the ones in Transformers or Pacific Rim).

But rather, everyone should imagine it like this:

There it is. This child is super stupid. Think about it, think of the image of being stupid, stupid. Do not think of it as big black idols like Megatron (Transformers).

Here will be the work of the Programmers.

They would use some hell of a command line like this:

Generally, this is a list of rules and guidelines. So that when it matches a certain rule that has been defined, the robot will take out the instructions so that it will follow each step exactly without exception. This is called the [Develop] process.

And when there is a certain exception, also known as an error, it occurs:
  • 1 is that the bot will be "turned crazy", which means it doesn't know how to handle it, it struggles until it runs out of energy or something malfunctioning, or it will behave abnormally. lead to the error of itself or other components related to it.
For example: the closest and most familiar: when you use Windows, you are watching Ozawa artist perform but it says "Window Media Player not responding". It was because something couldn't do it and it kept trying to make its standstill.
  • 2 is it will ignore this case. Looks like don't know anything. It is true that it does not know. Haven't given it instructions so in this case, it does nothing.
So, a bot is considered wise or stupid. That's because the programmer for it has:
  • Predict how many cases.
  • When is awareness which is the case?
  • How to handle those cases?
So when you want to consider which robot is good or bad. It should be put into different circumstances and conditions. See how it works.

For example: an off-road robot, if you want to see if it really crosses the terrain or not, you have to try it through different terrains (sand, rock, gravel, flat, rough, slippery, wet,. ... even combining terrains together). This is called the [Testing] process. After [Testing], we will realize that this bot is better than terrain, and there are some terrains it cannot pass.

So when using a bot, with good topography, you do not have to worry much, but with the bot, terrain is a bit weak, let the bot just walk and pay attention to where to fall to help, and with the terrain. If so, let's just put it in the box.

After that, the robot will be tweaked so it can be improved (if necessary). This is called the [Tuning] process. (Like some car builders. Change, edit, add, or remove some things in the car to make it more suitable for you).

This [Testing] and [Tuning] process is continuous. When [Testing] looks good, then run it for real. After running, see some problem, Then go back to [Tuning]. And after each [Tuning] there's [Testing] again because we don't know how that change will affect the overall. So it cycles around between these two steps together. But note, [Tuning] will not help the off-road robot that can fly to the moon or dive into the sea. It just helps the bot perform better than what it has programmed for, it doesn't turn the bot into a superman.

And in fact, most robots are bots that perform one or several simple operations (Close the bottle cap, screw the screw, install components, ...). Mainly used in the production line. There are a lot of bots here, and each one is only doing one simple operation, not combining many things into one. The main purpose of this is to ease the [Develop] [Testing] [Tuning] steps I mentioned above. Because what is simple, it is easier to change, fix, or manipulate anything on it than to be complicated.

And even with things that are too complicated, sometimes it goes wrong, I don't know if it's wrong, and even knowing it's wrong, I don't know where it is wrong, and no matter where it is wrong, I still don't know. fix it so that it's all wrong. In the end, even if it is corrected, it's not sure that it's all gone wrong.

A long time about the robot, the purpose is to give you a better understanding of what a robot it is like, how to use it properly.

When using a trading bot. You should also pay attention to the above factors.

You are not participating in the [Develop] process, though. And you do not know how it is.

So you can just go through the [Testing] step. To see what the child does. How does it cross the terrains, or tell the context of trading how it can survive market conditions.

Then you can observe the results and can [Tuning] some parameters, then [Testing] again, if it is okay, then run it for real. During running unstable, go back to [Tuning] and [Testing]. Just go round and round. In trading, just hope that the "Unstable" it doesn't burn all your accounts.

The steps mentioned above, there is always an intervention hand and human observation, more or less. Therefore, when someone gives you a bot and says "Run this, you don't need to do anything, 1 day 1-10%". Then you should use caution. Because it may be that it runs perfectly in the current terrain. But with other terrains, I don't know. Maybe today the bot will hit full margin Bitcoin, tomorrow Bitcoin pumped up to 50k. So you must be careful, sometimes it is not good to be a billionaire when using bots like this (or vice versa).