Didnt find any other thread on this topic so I thought it could be good with some discussion on the topic. Do you guys have any tips or good practices for maintaining code, different indicators, strategies and different revisions of them using parts of each other? The revision control quickly turns into a mess with many strategies and instruments unless one has good practices.
The different scenarios I am thinking about are:
1. Strategy monitoring certain parameters and going long.
Exactly the same strategy is run for the short side. However requires its own chunks of code.
So when updating or making changes they have to be done in 2 places which is very error prone. Another option could be to use generic variables such as "NewWithTrendExtremeForToday" instead of "NewHighForToday". Anyone found a good solution for this?
2. Separating conditions monitoring and trade-logic. At the moment I am coding most of the price monitoring etc. into indicators which the strategies access and monitor for trade triggering. This way many strategies run on different instruments can use the same logic and components from the indicators. Anyone found a better way?
3. Running same strategies with small deviations on many different instruments. These small deviations I guess is best to try and code as far as possible as Parameters passed to the strategies.
Comment