Determining the level of a programmer by a piece of code?

Question

Career in IT

There are multiple code files related to the same component in a React application (component, unit test, etc.). What can you understand by looking at this code, and how much code do you need to see to understand the level of the developer?
Tried to search, but not satisfied with the search, if this issue has already been discussed, leave a link and I will delete this post.

Answer 1

I join the opinion above that the code can be very roughly estimated.
And, probably, the more serious the developer, the more difficult it is to evaluate only by the code.
IMHO, a lot depends on the specific component and the requirements for it.
I'll go from the obvious:
- cleanliness of the code,
- knowledge and use of ES6 features in the right places (arrow, interpolation, spread, destructuring),
- the ability to solve intermediate microtasks with a minimum of code, elegantly, easily readable,
- looking at the component, paradoxically, you can make an assumption, the programmer still writes in classes, or switched to functional components, but this is not accurate)),
- in connection with the previous paragraph, you can evaluate the understanding and use of the life cycle or hooks,
- approach to data storage: state, context, readax etc,
- if Redax, for example, then what is left in the component, what went into the action, is the reducer a pure function,
- JS or TypesScript...
When I started writing, I didn’t think that such a list will turn out ... It turns out that a lot can be estimated!)

Answer 2

The level of the developer is determined not only by the code

Answer 3

Suppose there is a certain Vasya who is sawing mobile applications alone. Sawing well, there is not a single bug in his code . Well, he's just a genius, and he double-checks his code a hundred times before publishing. Makes big money on it.
However, if you look at its code, then there you will understand the hell out of what's what. The so-called spaghetti code . He understands this code. But we, outsiders, don't. Obviously, in order to work in a team, Vasya needs to pump up some skills. But the question is different.
The question is, what level is the programmer Vasya. How to define it? Is he a bad programmer or a good one? And bad for whom? Personally, Vasya is normal, there is enough money for food, a yacht and a country mansion. Is it possible to understand its "level" from the code at all? This is not some kind of game where you can download your level, which is displayed in the corner as a number .
Here's an example fork:

• The code may be crooked, but coolly optimized. That is, it works as fast as it is generally possible on the technologies used.
  
• Or vice versa, the code is beautifully designed, with comments, divided into a bunch of small functions for ease of understanding, but it seems to have a mistake in the architecture itself. Bubble sort type.
  

Answer 4

Deadlines, compliance with technical requirements, code clarity.

Answer 5

What can you understand by looking at this code, and how much code do you need to see to understand the level of the developer?

You can understand:
a) How clearly he thinks in principle
b) How much he knows all the tricks of the language (knowledge of ES6 in the case of js)
c) How careful that others understand his code, that is, whether he gives clear names to identifiers, whether he neglects
It is difficult to say about the amount of code with comments , sometimes a couple of dozen lines are enough, if the code is complex, then immediately the video is the handwriting of the master. Sometimes there can be a lot of code, but it is simple and of the same type.
In any case, you can say very, very much in terms of code. But there is also the concept of architecture, this also applies to react applications, the ability to build an architecture does not always go along with the ability to code, although in 90% of cases they do, because all this is a consequence of clarity of thought.

Answer 6

Determining the level of a programmer by a piece of code?

Remember once and for all:
1. The coder is NOT a programmer,
2. The programmer solves the problem as he sees fit.
3. Coder - does what the programmer says.
The answer to the question: to understand the level of a developer (programmer) - you need to be at least at his level of intelligence and consciously not only understand the logic of his code, but also understand: why he chose this particular solution to the problem, and not another.