Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I see firing in such a case as a cop-out, a cowardly way to appease mob-mentality.

In this case if the employee responsible for firing the moderator did such acts repeatedly despite management warnings than perhaps it's a good idea to fire that person. However this doesn't seem to be the case, the CTO correctly assumed responsibility in his apology of green-lighting the moderator's firing.

He does the right thing, in my opinion, by promising a better process that wouldn't lead to such a hurtful (and seemingly unfair) dismissal.

You don't fire an employee for mistakenly deleting your production database, you update your process so this cannot happen (at least not by accident).



In some cases, that is true. In other cases, it is an important part of removing a toxic element from your organization.

There are some people who refuse to behave in the best interests of the group, no matter how much direction you give them.

...but you are correct that they are often only one part of the problem. Then again, often firing them will motivate some of their supporters to quit.

I imagine that was the impetus behind firing Monica, so perhaps turnabout is fair play.


> if the employee responsible for firing the moderator did such acts repeatedly despite management warnings than perhaps it's a good idea to fire that person

> There are some people who refuse to behave in the best interests of the group, no matter how much direction you give them

I think we agree on this.

If an employee refuses to change behaviour despite multiple warnings he/her is fair game for dismissal. However I think firing someone without prior warnings is abusive unless it's for something criminal or malicious. You can probably guess that I don't care much for at-will employment...




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: