A bigger issue is readability and maintainability.
Bingo! Someone once said that writing code is 20% of its cost, while debugging and maintaining the code is the remaining 80%. When I had my own software company, I usually assigned the coding task to small teams of 2 or 3 programmers. The typical time frame would be one or two weeks for a task. Each Friday, all of the programmers (small company with a max of 9 coders) attended a code walkthrough. If the team passed the code walkthrough, everyone got free pizza for lunch and everyone could leave early that day. The point: 1) different sets of eyes on the code are a test of its readability, 2) everyone had a least some idea of what each team was doing and how the pieces-parts fit together, 3) if one person went on vacation, it was easier for someone else to fill in, and 4) it fostered a we're-all-in-this-boat-together understanding. You'd be amazed how many times the programmers external the team were there long after closing on Thursday, just so they could get a free pizza and a few hours off. I think the result was more than worth the cost and it did produce better and more easily maintained code.