2) In addition to eropple's point about treatment of the new hire, I think it can be disruptive to the existing team to have a bad hire. For one thing, existing staff always have to spend a least a little time teaching a new hire how things work at the company, and that time is essentially lost if they don't work out. It also frequently means you'll have some mediocre/bad code sitting around when the employee leaves, or in the worst case they could inadvertently cause some major security/stability issues for your product. That can be somewhat mitigated by proper process and permissions, but it's still a risk.
2) In addition to eropple's point about treatment of the new hire, I think it can be disruptive to the existing team to have a bad hire. For one thing, existing staff always have to spend a least a little time teaching a new hire how things work at the company, and that time is essentially lost if they don't work out. It also frequently means you'll have some mediocre/bad code sitting around when the employee leaves, or in the worst case they could inadvertently cause some major security/stability issues for your product. That can be somewhat mitigated by proper process and permissions, but it's still a risk.