Well, maybe. It really depends and you won't know unless you're reading the code and cross-referencing with applicable unit/regression tests. Some of my most p

Well, maybe. It really depends and you won't know unless you're reading the code and cross-referencing with applicable unit/regression tests. Some of my most productive days have been in eliminating unnecessary/poorly written code, not in adding lines. But you can't do that unless you know: 1. What the program should do 2. What the specific code you're looking at is trying to accomplish vs. what it actually does Bringing #2 (what it actually does) into synchronization with what it's supposed to do can allow you to eliminate code, and the opportunities for reducing the overall amount of code grows as you look at a wider scope/% of the overall project. But it all depends.