Hired a friend who is kindoff a spoiled brat. If me or the rest of the team tell him anything he answers with the team does not know enough to tell him what to do. The slightest words (why is it not done yer etc. seem to trigger his ego and threaten to resign). His skills are also not what i thought they were , they get the job done but thats pretty much it. Should i work to placate his ego or let him resign.

Honestly just kick him out

Get rid of toxic.

Sounds like you’re gonna be losing a friend pretty soon

I say get rid of him only to find out that the next person you'll hire to replace him will be even less competent 👍

@hinst Yep , the hope on that would be that we would not have to deal with the bad attitude.

Tell him to harsh truth if he quits let him if he doesn’t change fire him.

Egos aren't Amigos

I know this type of rude arrogant coders. First of all this guy doesnt seem to value the opportunity that you gave him, because apparently he didnt have to bust his ass to get it, so he is ungrateful.

Second, if you already have problems that early then imagine what will happen few months or even a year in?

This guy will most likely stay on the same level that he is now (because he rejects criticism and probably will reject team standards/best practices because hey his code works!). Also he most likely will write lots of obscure code that only he will know how to operate with. So u will get an arrogant dev who will be hard to replace because he will manage create a lot of obscure code. This is how people like him survive by ensuring they are needed and can still continue being assholes.

And last point, when u are hiring new devs please have a decent tech interview (maybe even a task). Especially if its a friend!! Figuring out the actual level of developer when hiring him is a must.

@magicMirror I hate in general how that word is used but come on, that is not even a remotely valid sentence.
You can lower toxicity, get rid of toxic waste. Take out the poisonous element.

Or just say it how it is: Correct behaviour or get rid of the misbehaved that might negatively influence the teams moral, progress and culture.

I chose to retain him but gave him a stern warning, mostly becuase i still think he can improve. Lets see how this goes (will post in this thread if it does backfire). Maybe i was not hard enough. This person does xd files for us so i am not that worried about leaving behind unmanagable code.