Good research leads to good design resulting in a small amount of code in the right places that either: Fix a bug, Add feature set Do something new. My epithe

Good research leads to good design resulting in a small amount of code in the right places that either: Fix a bug, Add feature set Do something new. My epithet for one programmer was "He writes a lot of code" Extra code makes it harder for the next guy to figure out what's going on, and has more space for bugs. But that came from a "productive" developer and that code can tie down a dozen maintainers in dozens of customer sites. The productivity is job creation for a bunch of folks whose main ambition is finding a job where they don't have to work with crap code. I've done a number of projects where I got rid of multiples of code compared what I put in. The best example was where I replaced a subroutine with a single character constant.