7
Bikonja
7y

I feel like saying "I know C#" (or Java or other similar languages) to mean that you know it as a language as opposed to more of a framework is ridiculous. We should say what programming language level we know (high, mid, low...) since the difference between say C# and Java is pretty much the same as the difference between say WinForms and WPF. Depending on which two languages and which two frameworks you choose it can be a much bigger difference between the frameworks than the languages.
In a CV I'd like to say "I know x-level languages with experience in [actual programming language + frameworks]" instead of saying I know C# and then recruiters and HR people and such assume I don't know Java at all, but know MVC, WebForms and whatever else even though I might specialise in something else and would take me pretty much the same to get proficient in Java as it would take me to get proficient in that framework or something that's technically C#.
It just makes so much more sense to me. As a dev you're supposed to know the principles, the syntax should be secondary. A pointer is a pointer regardless of it's marked with a * or IntPtr or just a value in a register with no special marking that it's a pointer...
Can we, as devs, come up with something like this?

Comments
  • 1
    This seems like a good start. Similar to languagw thing, Ive seen too many job offers wanting experience in a specific api. So they dont want devs that can learn, just ones that limit themselves to a handful of apis? The problem is going to be that we need the HR people to understand it
  • 0
    @plumbus something simple for the HR people is one of the reasons why I want this type of classification - if you need an expert ask an expert, but if you need general devs you can use these simplified classifications
Add Comment