![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
You have no idea how much I am looking forward to turning in my notice at work. In fact, I've already gotten a copy of Johnny Paycheck's "Take This Job And Shove It" that I am getting more and more tempted to play...
I've been working on this current project for roughly six weeks now. It has been completed several times, only to have my Group Lead completely disregard the packet of specifications and programs I sent him, and tell me that we needed to add X, or change Y...
Well, lately he's been breathing down my neck about "We've got to get this done ASAP. Top Priority!" (Which is his code-phrase for "I've told someone it will be ready by such-and-such date, without bothering to check with the developer to find out whether or not that's possible.")
Yesterday he tells me that it *has* to be done that day. Fortunately, I'm far enough along that this is actually feasible.
At 4:30, I am able to successfully test everything. All of his latest changes are in place and working.
At which point he tells me that no, this and this and this are wrong... and gives me 13 major changes -- all of which he still wants done that night, and all of which have been in place since the very first version I sent him back in August, as well as every other version since then.
Basically, he's been told repeatedly over the past weeks about these things, but now at the 11th hour these huge changes *have* to be done... and so I end up being in the office until after midnight last night.
And it strikes me as odd that on the one hand he's insisting that these new changes are the way things were always supposed to have been, while on the other hand the directories and such that *he* sets up for use by this process don't exist for the new version, but only for the old one.
Why haven't I killed this man yet?
I've been working on this current project for roughly six weeks now. It has been completed several times, only to have my Group Lead completely disregard the packet of specifications and programs I sent him, and tell me that we needed to add X, or change Y...
Well, lately he's been breathing down my neck about "We've got to get this done ASAP. Top Priority!" (Which is his code-phrase for "I've told someone it will be ready by such-and-such date, without bothering to check with the developer to find out whether or not that's possible.")
Yesterday he tells me that it *has* to be done that day. Fortunately, I'm far enough along that this is actually feasible.
At 4:30, I am able to successfully test everything. All of his latest changes are in place and working.
At which point he tells me that no, this and this and this are wrong... and gives me 13 major changes -- all of which he still wants done that night, and all of which have been in place since the very first version I sent him back in August, as well as every other version since then.
Basically, he's been told repeatedly over the past weeks about these things, but now at the 11th hour these huge changes *have* to be done... and so I end up being in the office until after midnight last night.
And it strikes me as odd that on the one hand he's insisting that these new changes are the way things were always supposed to have been, while on the other hand the directories and such that *he* sets up for use by this process don't exist for the new version, but only for the old one.
Why haven't I killed this man yet?
Tags: