However, one criterion I disagree with is years of experience. I suspect (based on personal experience) that the variance of the other categories with respect to years of experience is a lot higher than one would think. So there's no real utility to including it.
Programmer's Competency Matrix for SDE hiring parameters (2008)
31–40 of 51 posts
Re: Programmer's Competency Matrix for SDE hiring parameters (2008)
#32Re: Programmer's Competency Matrix for SDE hiring parameters (2008)
#33Makes everything sound so mechanical and boring. Do they want normal people or some bot like creature that they can just assign numbers in a matrix? Depressing.
You don’t want to hire boring bot-like people, but you also don’t want a totally subjective hiring system full of bias. I think having an objective scoring of some sort is a good reference even if it’s not the final decision.
Re: Programmer's Competency Matrix for SDE hiring parameters (2008)
#34My thoughts: First of all, the third column here is highly editorialised. If you have a look at anything related to languages, he always lists Erlang, Oz, Prolog -- I wonder why? I won't go into a diatribe on this-or-that nonsense but it would be fairer to talk about languages by their capabilities i.e. either include more languages like Ocaml (which is my hill to die on for "high-society" languages) or just say "has…
I think the idea is that most people will start exploring the world of programming from higher layers working their way down. People use software, then they write software with tools (languages), then they try to understand the tools, then they try to understand what the output of the tools mean on a yet deeper level, going down the rabbit hole all the way down (to physics? but I guess the lines is drawn elsewhere).
This may be wrong but it's obvious from the rest of the matrix that this is probably just based on how the author and maybe their friends gained "proficiency".
None of this is generally applicable. I do think the,matrix is still valuable. It provides a view of how some people may evaluate competence (even if misguided wrt ordering/levelling) and provides a set of goals that are not bad per se. Being on the highest levels mentioned there does probably in fact translate to a certain high degree of experience and competence.
Re: Programmer's Competency Matrix for SDE hiring parameters (2008)
#35Earlier quoted context omitted.
Is nano really That Bad? It's always been good enough for my needs, and in the cases where it's not I generally hop on Sublime or vscode, make the changes I want to make, then paste it into my term.
It isn't, but frequently the default editor is set to vim. That said I would question the judgement of anyone that judges you based on your favored editor. Except emacs, those folks will burn in hell.
I feel that there is a strong correlation between overall competency and whether someone cares about their tools, and their passion for their editor is a way of getting hints of that
Re: Programmer's Competency Matrix for SDE hiring parameters (2008)
#36A lot of dismissive complaints that boils to "this is objectifying programmers", and yes I get it. But now I'm on the other side (VP, but still coding), and actively recruiting, I realized some things taken for granted from myself and my good engineers, are still missing from a large number of candidates I've interviewed so far. I usually ask the candidate for a live coding test over zoom. "Here's what you need to co…
Re: Programmer's Competency Matrix for SDE hiring parameters (2008)
#37My thoughts: First of all, the third column here is highly editorialised. If you have a look at anything related to languages, he always lists Erlang, Oz, Prolog -- I wonder why? I won't go into a diatribe on this-or-that nonsense but it would be fairer to talk about languages by their capabilities i.e. either include more languages like Ocaml (which is my hill to die on for "high-society" languages) or just say "has…
> As for the Systems Programming section, does he really think that knowing how a compiler works is a system-related topic?? and why is that level 1? shouldn't the first level be understanding things like system calls, filesystems, drivers, kernel operation? I think the idea is that most people will start exploring the world of programming from higher layers working their way down. People use software, then they writ…
Block-chain Dev, Android Dev, AI/ML devs are domain specific but in each of those there are atleast 3-4 domains mapping out in general from the PCM.
There will be a domain specific competency matrix on top of PCM.
Re: Programmer's Competency Matrix for SDE hiring parameters (2008)
#38Earlier quoted context omitted.
the IDE section is a bit dated. as a hiring manager, my belief is that IDEs are good enough (and even have collab features that are good in work-at-home-epoch) that it's not an unreasonable to never use/never have used vi/vim/emacs. If you're doing server administration, not being able to use vi is unacceptable; but these days everything is deployed by container and logging into raw linux systems is not really a thin…
Is nano really That Bad? It's always been good enough for my needs, and in the cases where it's not I generally hop on Sublime or vscode, make the changes I want to make, then paste it into my term.
Re: Programmer's Competency Matrix for SDE hiring parameters (2008)
#39Earlier quoted context omitted.
How do you standardize this across applicants? I'd worry that there's not enough to compare across candidates doing something as generic as this.
In my experience it’s used as a prescreen qualification- the actual interview of multiple candidates happens afterwards or in a second round.