Cycle #7, day 1 off:
Yesterday evening and today have been formidably productive.
I have integrated trade volume into my bad trade trap detection code. I have been working on that for the whole day yesterday. I resisted the temptation to go to bed before finishing. I absolutely wanted the code to be in place before going to bed so that the code can be tested while I was sleeping.
It turns out that I left 1 bug or 2 which made the code not work at all as expected and I did fix it this morning but I like to put goals to accomplish. I find that it helps to my productivity or otherwise, I don't see the days go by as I'm so absorbed into what I'm doing.
Actually, for now, I'm just collecting stats about volume that I am going to print when a trade opportunity is detected. I'm not sure yet how the current formula can be enhanced by incorporating volume data into it.
but this morning the trap detection code did save me from entering into 2 bad trades.... One of them did turn out to be a good pick after 20-30 minutes but entering it with what was known in the moment would have been gambling. My time horizon is much shorter than that.
So bottomline, I avoided possibly 2 bad trades but the system haven't traded at all... It appears that volatility is pretty quiet after the major BTC drop during the week-end...
I am also now supporting concurrent trade plan executions. I was limiting to 1 execution for the sake of being able to read the logs when problems occur. My confidence about the executions is now high enough to open the floodgate. This is very important for the profitability since for most of the time, opportunities are very scarce but when they happen, they tend to happen all at the same time. Limiting my system to only execute one plan at a time was making me leaving a lot money on the table.
This is of course a feature that I haven't tested yet but it is now in place on the server. I'm simply waiting it to be triggered to see if it will behave as designed...
Very cool times...
Upfate: 1 trade plan has been executed. Execution did not work as well as expected because of an odd subtlety that did happen. The weird result did allow me to uncover 2 remaining glitches in the code that I have immediately fixed. It was a very small price to pay to uncover those 2 glitches. I feel grateful for the problem that have happened.
Yesterday evening and today have been formidably productive.
I have integrated trade volume into my bad trade trap detection code. I have been working on that for the whole day yesterday. I resisted the temptation to go to bed before finishing. I absolutely wanted the code to be in place before going to bed so that the code can be tested while I was sleeping.
It turns out that I left 1 bug or 2 which made the code not work at all as expected and I did fix it this morning but I like to put goals to accomplish. I find that it helps to my productivity or otherwise, I don't see the days go by as I'm so absorbed into what I'm doing.
Actually, for now, I'm just collecting stats about volume that I am going to print when a trade opportunity is detected. I'm not sure yet how the current formula can be enhanced by incorporating volume data into it.
but this morning the trap detection code did save me from entering into 2 bad trades.... One of them did turn out to be a good pick after 20-30 minutes but entering it with what was known in the moment would have been gambling. My time horizon is much shorter than that.
So bottomline, I avoided possibly 2 bad trades but the system haven't traded at all... It appears that volatility is pretty quiet after the major BTC drop during the week-end...
I am also now supporting concurrent trade plan executions. I was limiting to 1 execution for the sake of being able to read the logs when problems occur. My confidence about the executions is now high enough to open the floodgate. This is very important for the profitability since for most of the time, opportunities are very scarce but when they happen, they tend to happen all at the same time. Limiting my system to only execute one plan at a time was making me leaving a lot money on the table.
This is of course a feature that I haven't tested yet but it is now in place on the server. I'm simply waiting it to be triggered to see if it will behave as designed...
Very cool times...
Upfate: 1 trade plan has been executed. Execution did not work as well as expected because of an odd subtlety that did happen. The weird result did allow me to uncover 2 remaining glitches in the code that I have immediately fixed. It was a very small price to pay to uncover those 2 glitches. I feel grateful for the problem that have happened.
