IMO the 10x productivity thing is a bit of straw-man. thats rarely the case. but realistically its more like 3-4x. I'd include one crucial factor in evaluating this that I always look for in new hires, its Ownership! Do you have commitment to your responsibilities or is it just about finding immediate gain (could be ego for brilliant jerks or security for mediocre lazy bum). IMO in long run if you are about avg you will converge on the 'right' solution if you are looking for it. the problem IMO is many engineers have weak sense of ownership of what they do & based on their capabilities they adjust their behavior.
I'd factor in the motives behind being jerk before judging. Is it that they are just mean egotistical person whose using his technical superiority or there is genuine desire to make things better even if it means 'breaking a few eggs' in short-term?
I worked with someone like that once and it made me conclude it does not really matter whether the intention is good.
If code review forces you to adjust hundreds tiny details according to someone elses preferences and opinions (as opposed to when you have something really wrong), you can not take ownership of that code. Because it is not your code in the first place. If you want people to take ownership and responsibility, you need to allow them to do so - not really possible when top dog is micromanaging them.
Imo, the developer in question should have work alone on some core part of the project he would have responsibility for and not do code reviews frequently.
I'd factor in the motives behind being jerk before judging. Is it that they are just mean egotistical person whose using his technical superiority or there is genuine desire to make things better even if it means 'breaking a few eggs' in short-term?