What To Do After You Fire a Bad Sysadmin Or Developer
Esther Schindler writes "The job of dealing with an under-performing employee doesn't end when the culprit is shown the door. Everyone focuses on security tasks, after you fire the idiot, such as changing passwords, but that's just one part of the To Do list. More important, in the long run, is the cleanup job that needs to be done after you fire the turkey, looking for the hidden messes and security flaws the ex-employee may have left behind. Otherwise, you'll still be cleaning up the problems six months later."
In fact, your entire corporate structure is at risk. How do you know he didn't engineer a brain virus that allows him to use the company's board members as flesh puppets?
He might have even used telepathy to cause major investment banks to sell him all of their shares of the company for pennies on the dollar. He might already own the company. It's best to double check.
In fact, he might be standing behind you right now, brainwashing you with lasers.
There's no -1 for "I don't get it."
Quickly leave the island before the dinosaurs escape.
My first reaction (before RTFA) was that the problem might not have been the employee, but the person doing the name calling. However, the link is to a blog that lists a generic list of precautions to take. Whoever wrote that blog still has some growing up to do, but I'll give him/her the benefit of doubt and assume they were going for humor.
In any case, I notice that HP paid for the content. Now we know why they are in such trouble.
Only the DEV got burned? - Either the manager cut corners & took risks by not hiring a tester. - Or he did hire a tester which didn't do his job properly. A decent tester would have spotted these shenigans long before launch, this probably would have saved you from burning the whole budget on an incompetent dev.
LOL. That would defeat the purpose of having a scapegoat in the first place!