Could it be the log failed? Then what do we do if Log failed. Will it get stuck? I was thinking maybe MethodBase.GetCurrentMethod failed???? Maybe…. Anyway, I thought could get the name dynamically instead of creating a variable. Maybe it might take more resources. It might not be able to deal with this.GetType()… But then it is usually fine…. If it cannot be used, surely will fail 100% of the time.
The amount I spent on learning before applying actually costed me more money until I do enough work. Still learning process is still needed even while working. Doing things subconsciously can make the easiest problem complicated. Could be your old habits or subconscious typing or the auto correction? hm.. This one is more like my habit. It is a hard to catch error when we did like that. I was thinking what goes wrong and no matter what I did, it would not return my desired results. Turned the code that I wrote previously and just a line only which I overlooked while checking, was blocking the rest of the changes… Dangerous code is the counter code that you wrote to right a wrong or blocking the wrong from working. That’s normally a temporary solution but the solution turned out to be preventing me doing other works… sigh… 😮💨 Today’s a lucky day and I found it while doing another part… so it is good not to always focus on one problem. The other problem could be the c...
Comments
Post a Comment