cycle 3. Stage 1 day 6:
My UMS journal starts to reads like a DMSI journal but sexual fulfillment appears to be important to me currently...
I got 2 sex proposals falling on my lap today out of the blue... I invited to my place one of the prospect and this resulted into great and amazing sex... She did stay for about 3 hours...
It is too early to say if this encounter will result into a relationship of any sort...
No idea where all this attention is coming from... It is a bit unusual to me to receive all this attention... I must have changed something in my own sexual marketing without being aware of it...
It is funny that the simple intention of running DMSI without actually run it is bringing me all the action..
that being said... I had a hard time to concentrate on moving forward the exchange migration project... I did move it a little bit forward but it is not fast enough for my taste... I suspect that there is some unknowns in the design that instead of confronting directly the difficulty, I perform some sort of procrastination instead... but I feel that unconsciously, I am organizing my ideas in my mental space... so I have hope that soon, my productivity will unblock once the mental design picture gets clear in my mind...
For one thing, since it is my first framework reuse, I am realizing that its current design lack of modularity. There is a lot of dependencies between the different components... I am not too sure if I can improve that aspect because there are real dependencies between the modules... It is not due to sloppy design... but it annoys the heck out of me because in order to make my next test, I needed to port a module which depends on another one and when the port of the second module is completed, I discover that this one depends on a thirds one and so on...
Without all those dependencies, I could rapidly write one module and try it out... now I need to port the whole thing before making any test at all. The best analogy is getting your finger stuck into some gears and the gears end up ripping your whole arm...
time spent on creating a new exchange layer is not wasted... Everything that I write will end up being used... It is just that more needs to be written before being in position to test... which is not very agile methodology friendly...
Writing this entry did help me figuring out a way to reduce the dependency issue... by creating some class hierarchy...
I could have a BaseExchangeContext with minimal functionality and a FullExchangeContext offering the full API... I am not sure that there would be a use to start passing those 2 interfaces around but just for the sake of testing faster partial implementation, it might be worth the effort... I'll think about it....
My UMS journal starts to reads like a DMSI journal but sexual fulfillment appears to be important to me currently...
I got 2 sex proposals falling on my lap today out of the blue... I invited to my place one of the prospect and this resulted into great and amazing sex... She did stay for about 3 hours...
It is too early to say if this encounter will result into a relationship of any sort...
No idea where all this attention is coming from... It is a bit unusual to me to receive all this attention... I must have changed something in my own sexual marketing without being aware of it...
It is funny that the simple intention of running DMSI without actually run it is bringing me all the action..
that being said... I had a hard time to concentrate on moving forward the exchange migration project... I did move it a little bit forward but it is not fast enough for my taste... I suspect that there is some unknowns in the design that instead of confronting directly the difficulty, I perform some sort of procrastination instead... but I feel that unconsciously, I am organizing my ideas in my mental space... so I have hope that soon, my productivity will unblock once the mental design picture gets clear in my mind...
For one thing, since it is my first framework reuse, I am realizing that its current design lack of modularity. There is a lot of dependencies between the different components... I am not too sure if I can improve that aspect because there are real dependencies between the modules... It is not due to sloppy design... but it annoys the heck out of me because in order to make my next test, I needed to port a module which depends on another one and when the port of the second module is completed, I discover that this one depends on a thirds one and so on...
Without all those dependencies, I could rapidly write one module and try it out... now I need to port the whole thing before making any test at all. The best analogy is getting your finger stuck into some gears and the gears end up ripping your whole arm...
time spent on creating a new exchange layer is not wasted... Everything that I write will end up being used... It is just that more needs to be written before being in position to test... which is not very agile methodology friendly...
Writing this entry did help me figuring out a way to reduce the dependency issue... by creating some class hierarchy...
I could have a BaseExchangeContext with minimal functionality and a FullExchangeContext offering the full API... I am not sure that there would be a use to start passing those 2 interfaces around but just for the sake of testing faster partial implementation, it might be worth the effort... I'll think about it....