Mid-year reviews

Most companies have a very formal process for performing reviews, usually once or twice a year. I will admit to shirking this duty (the formal review) during my tenure as a Director of Technology. The circumstances were really to avoid the pay discussion since we were in a pay freeze, and I regularly met with my employees to ensure they were being coached and mentored. Not to make an excuse, only to provide an explanation. 

So now my company is into the mid-year review season. I don't have to do these being an individual contributor (meaning I have no direct reports).  But I have seen some of the suggested metrics for our IT partners, specifically software developers. I think they're ridiculously silly and not applicable to today's modern developer. What do you think?

Metric Title

1. Achieve _____ % bug-free code for delivery to production.
2. Decrease defect rate by _____% by (date)
3. Document 100% of coding changes
4. Identify application development process improvement ideas by (date)
5. Increase code production rate to ___(#) lines of code per (unit of time) by (date)
6. Increase mean time to failure __% by (date)
7. Learn __(#) new programming languages by (date)
8. Provide work estimates for programming tasks that are accurate within ___% of actuals
9. Recommend new programming languages for inclusion in toolkit by (date)
10. Reduce mean time to repair failures ___% by (date)
11. Reduce rate of errors per lines of code ___% by (date)

Now that you've read the list, please comment! 

I'll start - at first glance, I think there is only ONE valid metric. ALL of the others are either things you should be doing NOW at 100%, things that have ZERO impact on quality or performance (like #5), or are so dependent on environment and others as to be easily gamed (#6) 

Which one is my personal favorite? #8 - Accurate estimates will reward you, your manager, and your team beyond expectations! Why? The credibility gained for being honest, accurate, and reasonable 100% of the time is extremely valuable to your clients - internal or otherwise. It means you know what you are doing, have architected an intelligent design and that you fully understand everything associated with providing a great product! It means that your clients can plan for (and count on) your delivery!

What do you think? Ready? GO!