DEV Community

[Comment from a deleted post]
Collapse
 
leightondarkins profile image
Leighton Darkins

Overall, that doesn't sound like the kind of person I'd like to have on one of my teams. Setting aside some time for "real talk" with the individual in question, to deliver some pointed feedback, would be a good place to start.

Outside of delivering feedback and trusting them to straighten up. You could also consider pair programming with this person. It's super great way to ensure that poor code never makes it past a devs local environment. It's also a good way to discuss the reasoning behind code design and style decisions so folks can better understand the "why" behind the things you want from them.

If they continue with the "zero care" attitude despite these efforts, this sounds more like a "people" problem, and they may need to be kindly asked to leave.