more tire stuff
Nov. 8th, 2004 01:09 am![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
awhyzipRemember when I had the flat tire? Remember how I thought that the only place around here I could get it replaced was Natick? Remember the dark bold-face text of doom on that place?
On Thursday I learned that 1) tires can sometimes be plugged rather than replaced and 2) this puncture was too large to be plugged. On Friday I learned, 1) Dedham is a reasonable distance away -- plus the pre-existing knowledge that 1) Dedham is not Natick and 2) there is a Town Fair Tire in Dedham. Ergo, a plan: Friday during lunch, I would drive to Dedham and replace my flat tire at last.
So, lunch time rolls around, and I'm not hungry so I put it off. Then I am in a meeting where much new work is added to my "plate". And this is good, but scary, but good. We found & fixed a pretty big bug right at the end of the week, and version 1.1 is ready at the same time. The developers had to deal with the fact that our source-control system doesn't like to develop two versions at once (deal with that and with and their actual work, of course). I don't like that the tool makes their life harder! I want to defend them from it, but of course, what can I do about that? Nothing; it's not anywhere near my job. And I've got my own tool that makes my life harder: our bug-tracking system. I swear the thing just ATE one of my bugs!
It's an annoying system. It's online, which is nice, but it uses an annoying frameset and every so often will reload the whole thing inside one frame (doubling up the menus) or will navigate to only one frame (leaving you trapped in that one function). My main beef is that its search functions are no where near powerful enough. Also it annoys me that when I make custom "reports" (in order to get around the weak search), it only lets me filter on some-but-not-all of the fields -- and of course those fields include two of the approx six that I am most often interested in. ANYWAAY, I was going to mention how at this meeting, just before they told me that both versions are ready for testing NOW, they also said that I should start working on some of the demos that we show to people.
I was a little happy to get to work on the demos, because I always like doing new things!
But then, as there was more and more for me to do in a tiny time-frame, I started to get worried. P. looks out for me, now that she is -- oh i forget the whole title -- manager, but I do tend to think I can do a lot more than I really can.
So I'll skip the story about how the tracker ate my bug, which someone important subsequently experienced and I was unable to demonstrate that it was known. I was secretly embarrassed. This was above-mentioned last-minute necessary fix. I'd previously not thought it was so serious, which also embarrasses me.
But enough on that; I was talking about tires. Just wanted to explain to you why it was not until 3:30 that I went out to run for the tire. Meaning it was already 3:30 when I discovered flat tire number two!
Yes, that's right: this time on the opposite corner.
"AUGH!", I cried, with a good dose of bitter humor, "This is NOT a weekly event!"
On Thursday I learned that 1) tires can sometimes be plugged rather than replaced and 2) this puncture was too large to be plugged. On Friday I learned, 1) Dedham is a reasonable distance away -- plus the pre-existing knowledge that 1) Dedham is not Natick and 2) there is a Town Fair Tire in Dedham. Ergo, a plan: Friday during lunch, I would drive to Dedham and replace my flat tire at last.
So, lunch time rolls around, and I'm not hungry so I put it off. Then I am in a meeting where much new work is added to my "plate". And this is good, but scary, but good. We found & fixed a pretty big bug right at the end of the week, and version 1.1 is ready at the same time. The developers had to deal with the fact that our source-control system doesn't like to develop two versions at once (deal with that and with and their actual work, of course). I don't like that the tool makes their life harder! I want to defend them from it, but of course, what can I do about that? Nothing; it's not anywhere near my job. And I've got my own tool that makes my life harder: our bug-tracking system. I swear the thing just ATE one of my bugs!
It's an annoying system. It's online, which is nice, but it uses an annoying frameset and every so often will reload the whole thing inside one frame (doubling up the menus) or will navigate to only one frame (leaving you trapped in that one function). My main beef is that its search functions are no where near powerful enough. Also it annoys me that when I make custom "reports" (in order to get around the weak search), it only lets me filter on some-but-not-all of the fields -- and of course those fields include two of the approx six that I am most often interested in. ANYWAAY, I was going to mention how at this meeting, just before they told me that both versions are ready for testing NOW, they also said that I should start working on some of the demos that we show to people.
I was a little happy to get to work on the demos, because I always like doing new things!
But then, as there was more and more for me to do in a tiny time-frame, I started to get worried. P. looks out for me, now that she is -- oh i forget the whole title -- manager, but I do tend to think I can do a lot more than I really can.
So I'll skip the story about how the tracker ate my bug, which someone important subsequently experienced and I was unable to demonstrate that it was known. I was secretly embarrassed. This was above-mentioned last-minute necessary fix. I'd previously not thought it was so serious, which also embarrasses me.
But enough on that; I was talking about tires. Just wanted to explain to you why it was not until 3:30 that I went out to run for the tire. Meaning it was already 3:30 when I discovered flat tire number two!
Yes, that's right: this time on the opposite corner.
"AUGH!", I cried, with a good dose of bitter humor, "This is NOT a weekly event!"
