Ester Shindler asked a question on LinkedIn the other day and summarized in an article for CIO Magazine. She asked,
"Who's the worst programmer on your team? How can you tell?"
We all can point a finger at the one person in our group who should be let go, we all know which code generating wildebeest should be eaten by the pack of lions nipping at our binary heals. But what metrics are we using? Here's the list from a recent CIO article:
- Don't care about the quality of work
- Cost the team in time and frustration
- Have a poor sense of timeliness
- Don't offer nor ask for help
- They ask the wrong questions
/dev/kde
No comments:
Post a Comment