Yamato
Legendary member
- Messages
- 9,840
- Likes
- 246
Replying as I read.
The problem with stoplosses is not only that they complicate things and have many negative implications (adding a stoploss increases the danger of over-optimization, as you're adding an extra parameter), but also that in back-testing they do not add profitability.
Yes, stoplosses would have some advantages: I would know how big my biggest loss could be. But the advantages of things being the way they are now are more, so I am not considering adding them. Also, with 120 systems created and a humongous infrastructure with 7 excel files, being burned out... it is simply not worth it, practically impossible. In this field, I have learned from the beginning that I just have to say "no" from the start, and not start doing something I cannot conclude.
The same applies to trying a different platform. Huge implications. It's like starting a new business. You have a restaurant, it took you years to get it going, and you're telling me to dismiss it and turn it into a swimming pool
Oh, good point. I read it only now: "I know that is a massive change and a lot of work with 120 systems though...".
I can't get started on this now. However I thank you for the detailed feedback and advice. But it's just a route I cannot get started on. I mean: we're talking about one year of extra work without any clear advantages (as I said there are more disadvantages than advantages).
The problem with stoplosses is not only that they complicate things and have many negative implications (adding a stoploss increases the danger of over-optimization, as you're adding an extra parameter), but also that in back-testing they do not add profitability.
Yes, stoplosses would have some advantages: I would know how big my biggest loss could be. But the advantages of things being the way they are now are more, so I am not considering adding them. Also, with 120 systems created and a humongous infrastructure with 7 excel files, being burned out... it is simply not worth it, practically impossible. In this field, I have learned from the beginning that I just have to say "no" from the start, and not start doing something I cannot conclude.
The same applies to trying a different platform. Huge implications. It's like starting a new business. You have a restaurant, it took you years to get it going, and you're telling me to dismiss it and turn it into a swimming pool
Oh, good point. I read it only now: "I know that is a massive change and a lot of work with 120 systems though...".
I can't get started on this now. However I thank you for the detailed feedback and advice. But it's just a route I cannot get started on. I mean: we're talking about one year of extra work without any clear advantages (as I said there are more disadvantages than advantages).
Last edited: