Can programmer experience be quantified?

Question

Programming

Knowledge of English can be conditionally determined by vocabulary. For example, knowing:
500 spoken words - basic level;
3000 words - intermediate level;
From 8000 free possession.

Is it also possible to quantify the programmer's knowledge? For example, by the number of functions.

Thanks everyone for the replies! ))

Answer 1

You can memorize all the English words, but be unable to form a phrase out of them.
It is the same in programming, if you know all the functions by heart, this does not mean that you can link them into a working program.

Answer 2

It all depends on what you want to understand in the end. Start from this and set the criteria for evaluation.
Your example of English proficiency

, can be conditionally determined by vocabulary. For example, knowing:
500 spoken words - basic level;
3000 words - intermediate level;
From 8000 free possession.

will only show the knowledge of the number of words. Skills from the application in oral speech, reading, understanding the interlocutor, these figures will not show.
I hope you understand what I mean.

Answer 3

The universal rule of how much they pay is so good. Everything else is crap. Although this is a controversial assessment.

Answer 4

Can programmer experience be quantified?

Can...

Answer 5

Impossible, since one programmer will be strong in one, another programmer will be strong in another. And this cannot be expressed quantitatively, even if you try to somehow average it, there will still be no metric. That is why the USE, IQ, the number of memorized English words are crazy metrics that can only show the ability to solve a certain set of some tasks from the USE / find associations by the type of circles with squares in the IQ test / remember some set of words and their meaning in another language.

Answer 6

quantify programmer experience

You can write the number of necessary / important programs

Answer 7

In general, I would say this:
The quantitative experience of a programmer cannot be measured, since in any project certain knowledge is needed, and not in general, everything, everything, everything. Many become obsolete, so a huge amount of knowledge and a large amount of knowledge easily compete depending on how relevant and in demand they are.
It is extremely difficult to assess the organizational knowledge that is needed for team leadership and architectural decisions.
Therefore, any quantitative experience is measured in specific metrics tied to a specific project/case, and these data are likely to be irrelevant for other cases/projects.