[simpleTruth]

Which would be rewarded in your situation, building 30 really simple pages by hand or spending 1/2 that much time to code something which generated those pages automatically?

Once again, the best programers write as little code as possible which allows them to focus on quality over quantity. It's easy to turn 10 lines of code into 20 classes and gain nothing, it's much harder to see those 10 lines of code once someone has written the 20 classes.

[stcredzero]

Which would be rewarded in your situation, building 30 really simple pages by hand or spending 1/2 that much time to code something which generated those pages automatically?

This method doesn't have web pages in mind. More along the lines of something like domain models for something like energy trading.

Writing tests for 20 shallow, repetitive classes would result in 20 shallow looking test classes, and that programmer would be called on it.

Web pages are really a narrow area of programming.

Once again, the best programers write as little code as possible which allows them to focus on quality over quantity.

How many functional specs are they accomplishing while they are doing this? I've known programmers who've created "entire new functional sections" in their app with 25 lines of code. Your issue is addressed by paying attention to functional specs.

[simpleTruth]

Look, all metrics can be gamed.

Take an existing project find all the places that link to each section of code and you have some idea how reusable things are. Tell people your doing this ahead of time and you promote spaghetti code. Ask people how difficult an objective is and you get a wide range of biases based on how you use the information etc.

The secret is not how to get the most reliable data, it's how to get the best outcomes including they way people try to game the system.

[stcredzero]

Look, all metrics can be gamed.

Look, now it's obvious you didn't carefully read the original comment! (Left as exercise.)