What is the difference between a beginner's code farmer and an advanced code farmer?

What is the difference between a beginner's code farmer and an advanced code farmer? It sounds like a very obvious problem, but is it so simple? What is the difference between a beginner's code farmer and an advanced code farmer? It sounds like a very obvious problem, but is it so simple?

I have heard of some coders in the company discussing this issue. At that time, one of my senior coders was discussing some other things with two junior coders. After the discussion, one of the primary coders raised this question. The primary coders are still senior coders.

The senior code farmer happens to be one of the best and smartest code farmers I 've ever had the honor to work with. From his perspective, it took 30 minutes to explain the difference.

The conversation is mixed with the general answer. the novice coders who raised the question (a little clever guy in the company) tried to split the question into two subquestions, in my opinion, this is an interesting, exploratory, and useful subproblem:

1. Objectively speaking, how can I determine when I became a "senior code farmer" as a primary code farmer "?

2. as a senior code farmer, how do you measure the progress of the preliminary code farmer? how do you know when a junior code farmer has crossed that road to become a senior code farmer?

Question 1

I think the first question is particularly interesting. As the office discussion continued, I tried my best to think about the issues that I had been thinking about over the years, from starting software development to becoming a developer.

There is no doubt that time is an important factor for every developer to grow into a person of higher rank. Observe various recruitment information over the years (some people think "advanced" means at least 5-7 years of experience, while others think it means at least 10-15 years ), obviously, there is no real "standard" for how long it takes for the professional time ".

After just a few years, some developers think they are senior code farmers, while others think they are only "intermediate level" after 7-10 years ". As a recruiter, I know all the above facts are true. These are beyond all doubt and are clear common sense. It is also interesting to be conceited. There will be different opinions on "How long is the time", and such "impedance mismatch" will cause a dispute.

Is it related to the technology or language type you have learned? There is a kind of academic opinion that mastering one or two languages can also become a senior coders, as long as he has mastered how to deal with problems encountered in the use of programming languages. However, another profession focuses more on working with different similar technologies and uses different technologies to solve more general problems.

It is clear that it depends on what you want to do at work. From that point of view, it is useless to internally discuss whether you have entered the "advanced code farming" field.

After a long discussion, I concluded that the internal judgment on the first problem is quite different from the previous one. If you ask me to propose a standard-whether informal or not-it will be: as a primary code farmer, when a company or team of senior technical staff asks you to do something, you have the level of comfort and confidence you have.

Question 2

There is no doubt that there is no quantity to answer this question. Frankly speaking, I haven't seen any solution that can be used as a silver bullet or gold scale to measure all the senior coders.

Yes, there are many tests and tests used to evaluate a developer's competency level. There is no doubt that these quizzes cannot be ignored.

What makes things even more interesting is that sometimes those who determine what a "senior coders" are not very familiar with the technology or language. For example, in a small company, a technical department expert may be a Java developer with a considerable number of Java Business program deployment experience. However, the same experts may be responsible for recruiting senior iOS developers. In the absence of advanced iOS development codes, some people have to go top and become experts.

Hold on, I am a little confused. The real problem here is to evaluate the progress of the novice coders.

There are some possible standards, most of which do not seem easy (not impossible) to properly communicate to the novice coders themselves. Once again, if it is required to provide a possible standard, I think it is such a standard that developers can give an estimate of the workload for a task or a series of tasks (no matter how large, be confident to complete it within a reasonable time range (don't let me give a task estimate), with minimal assistance.

In other words, if you are still making the same mistake, this mistake is the one you encountered when you first started development, then you are sure, you have not entered the field of senior coders.

Conclusion

This article is not intended to answer my question about the savvy novice coders. On the contrary, it leads to a discussion about what standards can be reasonably applied to every question. it is a starting point if you think it is good.

What do you think? What standards can be applied on both sides? We do not have a mature human resources department, but there may be something we can learn and understand.

Leave some comments for us to continue.