Fire Your Best Programmer

Mon, 28 Apr 2008 16:57:54 GMT

More and more, I'm coming to the conclusion that who managers think is their best programmer, is often their worse. So, managers could fire their best programmers and improve their organizations. Here's why. If you ask a junior programmer to develop a component to retrieve NS records, then he'll like write a class called DNS.NameServers and implement a public method like Get(domain) return IP[]. Ask a senior programmer and he'll write a DNS library with classes like Request, Response, Resolver, etc. They likely will take approximately the same time, the junior writting 200 lines of code and the senior writing 20,000 very well documented lines. Which do you think is easier to maintain? Which do you think is easier to use?

Cool Programming

Fire Your Best Programmer