Long story short, we have a piece of software my division developed for another Business Unit, under a completely different section of the hierarchy for my massive current company. We did it as a favor to them. I inherited the software, and have been added features to it and maintaining it for over a year.
Fast forward to now, and another long story short, the other Business Unit did and said some things which made the management of my division much less inclined to continue being in the software favors business for them (that's the polite way of putting it). That coupled with other things going on in my division, and the decision was made to offload their software on to them to maintain. That would include them hiring a programmer or two to maintain it, and moving their data off our databases, and also hosting it themselves, eventually.
That was about 9 months ago. They have had a VERY hard time finding someone who could find their ass with either hand, with a map. Some of their prior candidates actually contacted me to ask how to open Visual Studio (I wish I was kidding).
Their current candidate seems promising, but he has done stuff like asking me to provide things that are IN the source code repo he was provided access to, and asking me to explain common things like how a Stored Procedure works o_O
So, anyway, today the request came down for access to our Dev servers for their current candidate. He apparently has a build ready to deploy (which is fascinating, because the only database account he has access to that can still talk to our database, is his own credentials, which means if he is trying to do a Dev deployment, he has put his own credentials into the config file (or, god help me, hard-coded into) the application.
I pushed back and basically said, "um ... why don't I do a code review of this shizz, and then I can push the code to Dev, if it won't cause the End of Times?"
The response came back, "nope, sink or swim time, if they bork it, they bork it. If they have to roll back, then that is on them, give him access."
Yeah, um ... it is a ClickOnce deployment which uses the version number to control updates, so rolling back can be ... tricky. But, all right, whatever. I have granted this guy contributor rights to the directories he needs on Dev, may God have mercy on his soul, and my server =__=
I'll report back once he has tried to do something with it. He is in another time zone, so it may be later today, or Monday if he ends up doing it after closing today (because I haz important bizznezz to do on the weekends, that's why! :P)