Re:Programmer Competency Matrix
by nihilocrat on Thursday April 09, 2009 @12:55PM
(#554684)
On the same note, I don't see how 'trying out' a DVCS makes you suddenly level 3 on the "source code and version control" metric.
Programmer competency articles are sort of a macho, nerdy equivalent of "do these pants make my butt look big?"
Re:Programmer Competency Matrix
by monkeybusiness on Thursday April 09, 2009 @02:32PM
(#554885)
Yep. It's a dick measuring contest, geek-style. At least I'm going to call it that since I did so badly. It's amazing I get anything done. And yet . . . I do.
It absolutely is, but it is slightly useful to at least attempt to measure competency.
Though, this chart implies all skills are equally worthwhile. There's another extremely important category missing here, which I'll call "solving the right problem". It might need to be split into a technical side and a business/marketing side. Solving the customer's actual problem, and using the correct technical approach vastly outweighs many of the categories listed.
Re:Programmer Competency Matrix
by banned_man on Friday April 10, 2009 @11:20AM
(#556158)
"Solving the right problem" is like the skill of "big picture thinking". It's clearly important, but the evaluation of it is subjective and case-based. What's nice about this tool is that it's relatively objective, for the most part, although it certainly doesn't paint a complete picture of what makes a good programmer (which is context-driven, in any case).
Kinda like how ESR's "How to be a hacker" article is actually "How to be more like me".
You should strive for level 4: O(1).
for that, you need to be a mathematician
like coming up with n(n+1)/2 to sum integers from 1 to n
Hmmm, maybe my comment should read as: "it doesn't perfectly describe me in every way, hence it's a terrible list" ;) I'm getting too many 2's damnit!