![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
swestrupIt was an overcast day when I left for work, and apparently it rained on-and-off all day. Certainly there were puddles everywhere when I left work.
Work was as long and strenuous as I assumed it would be for a first day back from being sick. It took me most of the morning just to read all my mail, scan through the patch lists for relevant changes, and then synchronize my build environment to the latest version.
I wasn't planning to do the latter as I had been half-way through a "10-minute fix" on Friday when I was called away to a meeting, and never got back to it. I had wanted to finish the fix but it seems that Visual Studio is a bit over-enthusiastic about keeping me up-to-date, or else someone was messing with my computer while I was ill. In any case, I started getting dozens of bizarre errors that I hadn't been getting before. They looked like they were caused by someone having massively re-organized the code base (which had, indeed, happened) and I had gotten some random selection of updated mapping files. Oh. Joy.
So, after synchronization I discovered a brand new class of bug that was caused by us upgrading to new libraries over the time I was ill. It took a while to diagnose, with considerable help from others as I think I still have the dumb. Then there was heated discussion as to how best to fix this new class of bugs, and then it was pointed out that in my code I could make a simple change to avoid triggering the bug, and we'd wait until it bit the NEXT person to decide how to properly address the issue.
So, I did that. Then I went to run some test cases to make sure everything was working, and all my test cases were missing. I'm guessing they were stored in a directory that went bye-bye during the code-base re-org.
So, I spent a while rebuilding my test files, only to discover that one of the test cases that has always worked before, is now failing. Everything else works fine though.
By then it was time to leave, and so I did. So, I figure it will take a few hours tomorrow to track down this last bug and finish my "10-minute fix". Grumph.
Now that I am home, I am planning to cook myself supper (a breadless Philly cheese-steak) and then I am likely to simply collapse.
One thing I REALLY need to do though is figure out if I'm going to this Steampunk convention on the weekend. It starts tomorrow afternoon, and I haven't gotten a ticket or anything, although I'm told there will be a limited number available at the door. The question is, am I well enough? I've been quite ill all week and I'm not sure its wise to plan anything too strenuous for the weekend. I may be better off just limiting myself to the NaNoWriMo kickoff event, and spending the rest of the weekend relaxing and finishing my recovery....
Decisions, decisions.
Work was as long and strenuous as I assumed it would be for a first day back from being sick. It took me most of the morning just to read all my mail, scan through the patch lists for relevant changes, and then synchronize my build environment to the latest version.
I wasn't planning to do the latter as I had been half-way through a "10-minute fix" on Friday when I was called away to a meeting, and never got back to it. I had wanted to finish the fix but it seems that Visual Studio is a bit over-enthusiastic about keeping me up-to-date, or else someone was messing with my computer while I was ill. In any case, I started getting dozens of bizarre errors that I hadn't been getting before. They looked like they were caused by someone having massively re-organized the code base (which had, indeed, happened) and I had gotten some random selection of updated mapping files. Oh. Joy.
So, after synchronization I discovered a brand new class of bug that was caused by us upgrading to new libraries over the time I was ill. It took a while to diagnose, with considerable help from others as I think I still have the dumb. Then there was heated discussion as to how best to fix this new class of bugs, and then it was pointed out that in my code I could make a simple change to avoid triggering the bug, and we'd wait until it bit the NEXT person to decide how to properly address the issue.
So, I did that. Then I went to run some test cases to make sure everything was working, and all my test cases were missing. I'm guessing they were stored in a directory that went bye-bye during the code-base re-org.
So, I spent a while rebuilding my test files, only to discover that one of the test cases that has always worked before, is now failing. Everything else works fine though.
By then it was time to leave, and so I did. So, I figure it will take a few hours tomorrow to track down this last bug and finish my "10-minute fix". Grumph.
Now that I am home, I am planning to cook myself supper (a breadless Philly cheese-steak) and then I am likely to simply collapse.
One thing I REALLY need to do though is figure out if I'm going to this Steampunk convention on the weekend. It starts tomorrow afternoon, and I haven't gotten a ticket or anything, although I'm told there will be a limited number available at the door. The question is, am I well enough? I've been quite ill all week and I'm not sure its wise to plan anything too strenuous for the weekend. I may be better off just limiting myself to the NaNoWriMo kickoff event, and spending the rest of the weekend relaxing and finishing my recovery....
Decisions, decisions.
