> applies himself constantly (works after hours, weekends, during vacations). He writes at least 5x more code than me These are not good things. Ideally you s

> applies himself constantly (works after hours, weekends, during vacations). He writes at least 5x more code than me These are not good things. Ideally you should want to ship as many features with as little code as possible, more parts mean more ways it can break. Working nights and weekends isn't good either, the schedule or scope need changed if people feel that's necessary. Please don't work during vacations barring emergencies, there's nothing good that comes out of that. I worked with someone like that too, and even though I'm pretty sure we made about the same, I made a lot more hour-for-hour, and my boss found my work perfectly satisfactory. He got more accolades, but I got more time with my family and friends. He also took more time than he thought to get things done, which deteriorated the situation further for him. I hope he's happy at the role he moved on to. In the face of something like this, I'd maximize my reliability. Sure you'll ship fewer features, but make sure you finish the stuff you start when you say you will, and make sure it absolutely is tested, documented, and functional. Hope that helped!