Selling conditions: If the stock opens lower and drops on the second day, and no strong upward attack is initiated, it should be sold at the second peak before it falls back; slightly, slightly, slightly.
Alright, a whole bunch of selling conditions have been written, but not a single clear number, and it's impossible to have a clear number.
[Sell immediately if profit is 5% or loss is 3%]
Simple it is, but such an all-or-nothing approach is destined to lose a lot of opportunities, leading to losses where gains could have been made – could have earned 30%, only earned 5%.
Thus, here it is necessary to use fuzzy judgment, flexibly adjust according to different conditions, rather than mechanically setting a number.
The most important task of a quantitative engineer is to write this part of the code.
It is a complete set of detailed rules for different situations that collectively build an elastic space for temporary judgment.
