[Stratoscope]

It's a little extreme to say that cold hard code is the only thing that counts. Years ago I worked with someone who contributed more cold hard code than anyone else I've known. A brilliant developer, probably one of those "10X" people they talk about: that rare combination of outstanding technical chops and "get the job done" productivity.

But more than once, he jumped into projects and features that he knew other people on the team were already working on, implemented them himself in a rush without coordinating with the other developers, and pushed his code instead.

Sometimes he would take shortcuts to get it done faster while his teammates were working on a more fully developed version of the feature. And since he was first, that was the code that would be used. The other developers were left with nothing to show for their efforts, less of a feeling that they were valued members of the team, and a significant loss of reputation in the eyes of management.

Cold hard code is important, of course. But it's not the only thing.

[nogbit]

Who was running that team? Blame should be on leadership for running an inefficient team where team members don't share and coordinate so that common projects, code, libs etc can be flushed out.

[pryelluw]

That's not brilliant, IMO. Just someone who knows how to program but not work on a team.