This is another opinion question.
I have multiple entry and exit signals, but some signals are disabled when other signals are in operation. But the way the communication works between the signals, I have a sort of common structure that has a set of boolean variables, flipping on and off these signals or setting state variables.
Over time, the "shared information" structure just got larger and larger and larger and the code is no longer aesthetically pleasing.
I'm just curious if any of you have run into such an ugly situation and whether you found a "clean" way to integrate cross-strategy communication. This central coordination point is not a performance bottleneck, but the structure has become massive. I'm trying to tear it apart and refactor it.
I have multiple entry and exit signals, but some signals are disabled when other signals are in operation. But the way the communication works between the signals, I have a sort of common structure that has a set of boolean variables, flipping on and off these signals or setting state variables.
Over time, the "shared information" structure just got larger and larger and larger and the code is no longer aesthetically pleasing.
I'm just curious if any of you have run into such an ugly situation and whether you found a "clean" way to integrate cross-strategy communication. This central coordination point is not a performance bottleneck, but the structure has become massive. I'm trying to tear it apart and refactor it.