News for hackers. Stuff that matters.

A comment on The Ten Commandments of Egoless Programming (2006). Parent comment

Re:The Ten Commandments of Egoless Programming (2006) by softbuilder on Sunday December 29, 2013 @11:47PM (#6983084)
At my first programming job one of the senior programmers left and we started calling his code "Billyware". His code was hard to maintain (written in several different languages, none of which he'd mastered) but I suspect the real reason the name stuck was because he was kind of a jerk.

One (of many) good things about collective code ownership is that this sort of blame game can't last very long.

[ Parent | on HN ]
Re:The Ten Commandments of Egoless Programming (2006) by midas007 on Monday December 30, 2013 @04:40AM (#6983857)
0. Cowboy coders that change horses midstream should expect to get soaked.

1. I make it a rule to fire the overrated jerks that (ca|wo|do)n't shape up, with poetic prejudice. <Evil hand rubbing ensues> For the "indispensable" ones that cause too many problems, it's harder but possible. There's might be no such thing as an irreplaceable employee, the worse situation is losing good people that are pushed away. (Fan of Github / Rackspace cultural practices.)

[ Parent | on HN ]