Stage 4, day 32:
Last Stage 4 day. My project did progress quite a lot in the last month. Beside that, I don't know what else to say. Because since it is the second month of lockdown, it feels very like the first month (aka stage 3). I hope things will get back to normal soon. It is not very fun. Seeing how USA citizens fight for their civil rights and liberties make me hopeful. US citizens have all my esteem to be courageous and fight for what they think is right instead of doing what they are told to do. They are liberty champions which will hopefully be followed all around the world.
I have completed 1 of the 2 improvements in the trade execution that I wanted to make. I did launch a test run and did capture 1 execution. 2 conclusions from the results:
1. New feature did work correctly
2. In this particular execution. It didn't help improving the yield because the spread was very narrow.
I'm much more confident that with the second element in place, it will become a winner. I did just address the low hanging fruit first. The second element is a little bit more complex to implement. I will roll up my sleeves and build it one block at a time.
Realistically, it will possibly take 2 days to complete.
Concerning my client performance issue. I did put that on hold but I have one more option that did pop out in my mind yesterday. Usually, when that happens, it is a very good sign and that means that I might be on the lead of a good solution.
I remember when I was reading the framework code. They use a View/Model pattern supported by a set of classes that my client is using. And the Qt framework table view class is pretty dumb. The pattern interface is permitting for the Model to be very granular. It can report to the view that 1 cell in the whole table did change and my code use that granularity fully by reporting single row or column changes. The framework provided table view is simply invalidating the whole table and fully redraw it. THIS must be incredibly expensive and dumb.
I'll take some time to see if it would be easy to replace the dumb framework table view for a clever and efficient one. I feel like it is something very possible to achieve. That wouldn't be the first time that I remove dumb Qt class with one of mine...
Last Stage 4 day. My project did progress quite a lot in the last month. Beside that, I don't know what else to say. Because since it is the second month of lockdown, it feels very like the first month (aka stage 3). I hope things will get back to normal soon. It is not very fun. Seeing how USA citizens fight for their civil rights and liberties make me hopeful. US citizens have all my esteem to be courageous and fight for what they think is right instead of doing what they are told to do. They are liberty champions which will hopefully be followed all around the world.
I have completed 1 of the 2 improvements in the trade execution that I wanted to make. I did launch a test run and did capture 1 execution. 2 conclusions from the results:
1. New feature did work correctly
2. In this particular execution. It didn't help improving the yield because the spread was very narrow.
I'm much more confident that with the second element in place, it will become a winner. I did just address the low hanging fruit first. The second element is a little bit more complex to implement. I will roll up my sleeves and build it one block at a time.
Realistically, it will possibly take 2 days to complete.
Concerning my client performance issue. I did put that on hold but I have one more option that did pop out in my mind yesterday. Usually, when that happens, it is a very good sign and that means that I might be on the lead of a good solution.
I remember when I was reading the framework code. They use a View/Model pattern supported by a set of classes that my client is using. And the Qt framework table view class is pretty dumb. The pattern interface is permitting for the Model to be very granular. It can report to the view that 1 cell in the whole table did change and my code use that granularity fully by reporting single row or column changes. The framework provided table view is simply invalidating the whole table and fully redraw it. THIS must be incredibly expensive and dumb.
I'll take some time to see if it would be easy to replace the dumb framework table view for a clever and efficient one. I feel like it is something very possible to achieve. That wouldn't be the first time that I remove dumb Qt class with one of mine...
