3 ms·
> Totally wrong. Read the original post: "he KEPT TRYING to parse JSON by splitting the string in Java" This rather fits with the other bit about "beaten into
by tempguy9999 7y ago
> Totally wrong.
Read the original post: "he KEPT TRYING to parse JSON by splitting the string in Java"
This rather fits with the other bit about "beaten into submission"
I have to assume from that text that he'd already been shown how to do it. If he could not understand that the easy way was easier than doing it the hard way, well pfffft.
It may be there's more subtlety here than was given, I dunno.
- crispyambulance 7y agoIt all depends on what one means by "already been shown how to do it". Something like that could easily be misunderstood/forgotten by the trainee or glossed-over by the senior. Or maybe he was just having a bad day. Whatever the case, learning often takes some amount of repetition before mastery is achieved. Real life work is not like stackoverflow, if you have a team that's your responsibility, you can't just downvote them to oblivion. Nor can you use performance on any one incident to decide to end someone's career in that particular workplace. Sometimes people just don't measure up to expectations, that's OK, it happens, but firing should be a decision based on a history of underperformance. Questioning whether or not someone is fit to "be there" should be something that is done upon deciding to start a PIP. Otherwise, it's just eroding the confidence and motivation of the individual and the team and, in many ways, is as bad as firing that person out of spite.