![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
What?! Is it extra fucking stupidity day?
Mar. 27th, 2007 09:05 amDo the Change people not have anything better to do?
RFC1 - I am the Requester, Coordinator, and Assignee (as I was told to do it by the Change team). That was 7 weeks ago.
RFC2 - I am the Requestor, Coordinator, and Assignee. That was 3 weeks ago.
RFC3 - I am the Requestor, Coordinator, and Assignee. Filed yesterday. Rejected yesterday because I am the Requestor, Coordinator, and Assignee.
Stupid, intrusive, overbearing and time-intensive red-tape I can deal with; I work in a megacorp, it is expected. Changing the rules partway through the process just adds insult to injury. Like my previous rants when Security changes the policy for accounts and groups when I am trying to automate and forcing DB schema naming when I am mid-project.
I must have poor timing. If I had done each of these things sooner, they would have gone through previous to the changes and been "grandfathered-in."
RFC1 - I am the Requester, Coordinator, and Assignee (as I was told to do it by the Change team). That was 7 weeks ago.
RFC2 - I am the Requestor, Coordinator, and Assignee. That was 3 weeks ago.
RFC3 - I am the Requestor, Coordinator, and Assignee. Filed yesterday. Rejected yesterday because I am the Requestor, Coordinator, and Assignee.
Stupid, intrusive, overbearing and time-intensive red-tape I can deal with; I work in a megacorp, it is expected. Changing the rules partway through the process just adds insult to injury. Like my previous rants when Security changes the policy for accounts and groups when I am trying to automate and forcing DB schema naming when I am mid-project.
I must have poor timing. If I had done each of these things sooner, they would have gone through previous to the changes and been "grandfathered-in."
