omg I work with a dude now who is brilliant, prolific and super-efficient - he successfully rolls out twice the number of features the next best person does, bu

omg I work with a dude now who is brilliant, prolific and super-efficient - he successfully rolls out twice the number of features the next best person does, but he leaves behind 0 comments ("code documents itself"), 0 unit tests ("unit tests are for rookies who are unsure about their code") and 0 documentation. How? How to get across the point that he's forcing all of us into the dead end when it comes to team scaling?