Junior Dev destroys PROD DB on first day.
-
@Kyle said in Junior Dev destroys PROD DB on first day.:
@JaredBusch said in Junior Dev destroys PROD DB on first day.:
@Kyle said in Junior Dev destroys PROD DB on first day.:
@scottalanmiller said in Junior Dev destroys PROD DB on first day.:
@jrc said in Junior Dev destroys PROD DB on first day.:
So the dude followed the instructions a little to closely and was fired due the results of that. F that noise. Not his fault at all.
No backup to restore? Also, not his fault.
Legal action against him, not bloody likely. If anything he has a case against them for wrongful termination.
Wrongful termination to cover up the person that fired you's mistake and then threatening you on top of it? That's a good combination for the HR to hear.
If he wanted to he could sue for his job back I'm sure.
Maybe. Many states have labor laws that allow firing during a defined onboarding period for any reason as perfectly legal.
In most cases it would be a probation period but it would all depend on his contract. Since he moved cross country to take the position I am sure there was a contract.
Even with a contract that said so, I'd say his case for bad faith is really strong.
-
@jrc said in Junior Dev destroys PROD DB on first day.:
@Kyle said in Junior Dev destroys PROD DB on first day.:
If he wanted to he could sue for his job back I'm sure.
They don't want to work for this company, no one does. If they are going handle such a reasonably understandable mistake in this manner I shudder to think how' they'd handle bigger issues. I mean, he could find himself charged with trespassing if he's 5 min late.
Yeah, he's lucky to be out of there. He needs to name and shame, though.
-
Yeah, if he decides not to go back, then he definitely needs to name them somewhere. I am sure local papers would be interested in the story. Though he should make sure that doing so does not expose him to legal action.
-
@jrc said in Junior Dev destroys PROD DB on first day.:
Yeah, if he decides not to go back, then he definitely needs to name them somewhere. I am sure local papers would be interested in the story. Though he should make sure that doing so does not expose him to legal action.
Firing him for no cause eliminates any realistic potential grounds that they have to silencing him.
-
Once you are hired, then they fake a mistake and fire you to cover things up.... you are pretty much free to do anything. If the story is true, he's almost certainly holding every, single card here.
-
I'd not go so far as to say they faked the mistake. But the certainly did set him up for failure by having actual admin credentials in their example in the manual that they mandated he work through.
-
@jrc said in Junior Dev destroys PROD DB on first day.:
I'd not go so far as to say they faked the mistake. But the certainly did set him up for failure by having actual admin credentials in their example in the manual that they mandated he work through.
Firing him is the tell tale component. Firing him only makes sense if there was something else going on.
-
Possibly. But it also could have just been a knee jerk reaction from the boss. Who know, perhaps they called him the next day, apologized, recanted the firing and asked him to return. Even so, I would not go back if I were him. Or at least not for any longer than it would take to find another job.
-
@jrc said in Junior Dev destroys PROD DB on first day.:
Possibly. But it also could have just been a knee jerk reaction from the boss.
Knee jerk reaction to fire the innocent party to cover up his own mistakes. Sure.
-
@scottalanmiller said in Junior Dev destroys PROD DB on first day.:
@jrc said in Junior Dev destroys PROD DB on first day.:
Possibly. But it also could have just been a knee jerk reaction from the boss.
Knee jerk reaction to fire the innocent party to cover up his own mistakes. Sure.
You can't see how someone who is completely panicked about the situation, frantically trying to work out what to do would not suddenly focus that negative energy on the person they perceive as the either the cause or a solid scape goat? Stress was through the roof, so it's understandable that someone could do what that boss guy did in the heat of the moment.
Not saying it's right, guy is an asshole and a shitty leader for just his reaction alone, just saying it's understandable on some levels.
-
@jrc said in Junior Dev destroys PROD DB on first day.:
You can't see how someone who is completely panicked about the situation, frantically trying to work out what to do would not suddenly focus that negative energy on the person they perceive as the either the cause or a solid scape goat?
He'd only be in a panic if it was his fault.... and... that's what it looks like.
Real problem is, it wasn't even a plausible scape goat.
-
@jrc said in Junior Dev destroys PROD DB on first day.:
Stress was through the roof, so it's understandable that someone could do what that boss guy did in the heat of the moment.
Not saying it's right, guy is an asshole and a shitty leader for just his reaction alone, just saying it's understandable on some levels.
So he's stressed. I don't see how that matters. You mentioned scape goating, which is the whole point. His reaction wasn't one of someone doing his job, it was of someone trying to hurt other people (probably to unethically protect himself.) Stress, sure, but that's no excuse and doesn't change what happened. So sure, I agree, he is probably still stressed that someone finds out what he did. But by firing an innocent party to cover up his own mistakes, he has more problems rather than fewer as far as worrying that people will find out. But bottom line, you are stating this as though stress being the trigger would change my assessment, but it does not. He's actions, motivation and the results remain the same.
-
If you mention it in a different context.... the bank robber was stressed and so murdered the witnesses.
That's great but "stressed" doesn't excuse the action, especially when the stress was the result of the guilty party. The CFO would not have been stressed here if someone (maybe him) had not screwed up to begin with. Just like the bank robber didn't need to rob the bank, the junior dev didn't need to be set up for failure. That the CFO or the bank robber chose to be in stressful situations and then use that as an excuse to do something far worse than the thing that caused the stress was their own choice and reverts the blame back to themselves again.
