![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
Long, bad, awful day.
Work is abysmal. Made some changes to an app. a week or so ago, and testing took longer for anyone to do than it should have, but it was mostly done, and everything was all ready to roll out... and suddenly the scope more than doubled two days *AFTER* the go-live date - plus a second "OMG! Emergency project that you never heard of before today, but it has to be done yesterday!!"
Rolled out the "OMG! Emergency!" one tonight, but checked emails this evening and found out that they had to roll it back because of a really bone-headed error on my part. My rational half knows that it's more their fault for the rush than it is mine, but tonight the emotional half is in control and I feel about two inches tall. I get so discouraged when things go wrong, and nothing ever seems to be scoped properly, so I'm always making changes to my little piece of the puzzle while *KNOWING* that no one's really done the legwork to make sure that the rest of the puzzle is going to fit together once the change is made.
AND THEN, I wasted at least an hour of my day today just convincing someone that his program had a certain error going on.
Me: I'm looking at some data, and it looks like your application is doing <THING A>, which is bad because...
Dev A: It can't possibly. My program doesn't even try to do <THING B>.
Me: I said it does <THING A>, not <THING B>. Here's what I see happening, and here's why it's bad...
Dev A: No, my program doesn't do <THING A> either. Doesn't even come close.
Me: (Pulls up *his* application, which I know almost *nothing* about, and takes screenshots of it doing <THING A>.)
Dev A: Oh. Gee, I guess it does do <THING A>. Is that a problem?
Seriously. He *LITERALLY* has the gall to ask me if it's a fucking *PROBLEM*.
So, then, on top of all this wonderfulness, I've got a second client having nervous breakdowns because they claim my application is just magically erasing data every few days. It's apparently been doing this for more than a year, and yet somehow they can't live with it for another day or two while I clear my schedule.
*AND* the boss is hiring someone to be an assistant-type person for me - which is dandy in theory, but which really means that I have to spend half my day tomorrow getting ready for an interview with this guy when I have never interviewed anyone in my *life* and have no idea what to say beyond "So, you know how to program, huh?" And then, once they're hired, it'll be a month (or two or three) of dropping everything to babysit the newbie 18 times a day.
And I still have "doubled-scope" project to finish up on top of the interview tomorrow, and I can't work late because the stupid cable guy is coming.
Sucky, sucky way to start the week. :(
Rolled out the "OMG! Emergency!" one tonight, but checked emails this evening and found out that they had to roll it back because of a really bone-headed error on my part. My rational half knows that it's more their fault for the rush than it is mine, but tonight the emotional half is in control and I feel about two inches tall. I get so discouraged when things go wrong, and nothing ever seems to be scoped properly, so I'm always making changes to my little piece of the puzzle while *KNOWING* that no one's really done the legwork to make sure that the rest of the puzzle is going to fit together once the change is made.
AND THEN, I wasted at least an hour of my day today just convincing someone that his program had a certain error going on.
Me: I'm looking at some data, and it looks like your application is doing <THING A>, which is bad because...
Dev A: It can't possibly. My program doesn't even try to do <THING B>.
Me: I said it does <THING A>, not <THING B>. Here's what I see happening, and here's why it's bad...
Dev A: No, my program doesn't do <THING A> either. Doesn't even come close.
Me: (Pulls up *his* application, which I know almost *nothing* about, and takes screenshots of it doing <THING A>.)
Dev A: Oh. Gee, I guess it does do <THING A>. Is that a problem?
Seriously. He *LITERALLY* has the gall to ask me if it's a fucking *PROBLEM*.
So, then, on top of all this wonderfulness, I've got a second client having nervous breakdowns because they claim my application is just magically erasing data every few days. It's apparently been doing this for more than a year, and yet somehow they can't live with it for another day or two while I clear my schedule.
*AND* the boss is hiring someone to be an assistant-type person for me - which is dandy in theory, but which really means that I have to spend half my day tomorrow getting ready for an interview with this guy when I have never interviewed anyone in my *life* and have no idea what to say beyond "So, you know how to program, huh?" And then, once they're hired, it'll be a month (or two or three) of dropping everything to babysit the newbie 18 times a day.
And I still have "doubled-scope" project to finish up on top of the interview tomorrow, and I can't work late because the stupid cable guy is coming.
Sucky, sucky way to start the week. :(
Tags: