What is the level of most programmers who have been working for two or three years?

I mean most of them, not just the crap. This question arises because I am currently learning PHP in a training institution, and I feel that the things taught are relatively basic. Then I read some codes on the Internet and read programmer topics on Zhihu. I feel that I don’t understand what they say, and then I feel that I am a lousy person. , and then compared with others in the class, they feel that they have learned better (I need to explain it here to avoid it becoming a shortcoming. I am not here to seek comfort or naively think that just because I have learned well in the training class, I will be highly skilled.). So I wanted to know what the level of programmers who have been working for two or three years (I heard is the fastest growing stage of technology) is like, and whether their skills are very strong. What are the salary levels for most people? Do you feel overwhelmed at work? Anyway, it’s because you are about to find a job. I hope to know more about the situation of programmers. Reply content:

Thanks for the invitation.

At the level of two or three years, basically (excluding diligent and motivated programmers), most of them are github porters. Although they have already entered the software industry, they are ignorant and regard the proficiency in using open source tools, libraries, and frameworks as their programming skills. The end, not the beginning.

They are still as concerned about salary as the current subject, but even more so. They have high ambitions but low power, and are impatient. What they think about is not how to improve their skills, but how to improve their salary level. If you kindly point out the problem to them, they will I'm still worried about you: There is a company willing to give me so much money, can you handle it?


Considering that it might be criticized by some people, I closed the review. You don’t need to follow “most people”
You should follow the Top 10.
Most people are definitely mediocre.
Paying attention to them will only make you mediocre than "most people".

Reply to the original poster’s question:
Most of them are bad, very bad.
No thinking, no summary.
Don’t touch code after get off work.
No one is allowed to say he is bad.
If you don’t buy a book yourself, if you buy a book, he will borrow it and not return it. Very annoying. Personally,
most programmers are engineers rather than scientists
In most cases, they are
using existing tools to solve practical problems
rather than building tools

With continuous in-depth work,
programmers begin to have With the ability to transform and create tools, the deeper you go, the deeper the tools you transform and create, which means the closer you get to the bottom, and the more you become like a scientist.
==================================================== ============
Construction engineers do not need to know how autoCAD is implemented,
As long as they know how autoCAD draws...
Engineers who use bolts may not need to know about these bolts Process details
As long as you know the various indicators and characteristics of this bolt, it will be fine.
The same goes for programmers...

I personally don’t like the concept of full-stack engineers...
In my opinion, the continuous subdivision of responsibilities and technologies
Let professional people do professional things
should be the direction of development Bar
================================================== =============== I have been working as an algorithm engineer for two or three years:
1. Able to write various scripts proficiently
2. 80% of the time writing scripts
3. Can name several machine learning algorithms
4. Complete dirty work easily (call me little brother Do)
5. I have become accustomed to unexplainable results, and I can forcefully explain them to convince the leaders
6. Before adjusting the parameters, I will go to the temple to burn incense sticks
7. There are many brand-new technical books piled on the table. Turn over. There is probably a book called "Statistical Learning Methods" Thanks for the invitation.

This is about a year and a half after I graduated.

As far as daily development is concerned, business logic, UI interface construction, some common performance optimization, less complex animations, etc. can all be easily solved. You can also build an app from scratch, including layering between modules and related exception handling.

Other obvious deficiencies are insufficient understanding of design patterns and architecture-related knowledge, and insufficient mastery of basic computer knowledge.
So I’ve been trying to learn more about operating systems recently, and I plan to write one myself. Later I will read Introduction to Algorithms and Compilation Principles, and I will also read books related to iOS development... Have you ever heard of CV God of War?
For programmers who have been working for two or three years, a large part of the code writing method is ctrl+C ctrl+V.
I think they are great because I have too little knowledge =. =
Of course, the amount of knowledge of an expert in two or three years can be very huge.
In short, it is easy to get started in programming but difficult to master.Modified on 2016.10.21
I was educated by a girl (well, yes, I am a programmer with a girl) and told me not to spread negative energy,
Well, actually I think this is indeed a common situation, and everyone has his or her own limits. , don’t do things that are too much beyond your own abilities (Brother Meng, don’t hit me, I also have dreams), which will only increase your troubles. Eating, drinking and waiting to die is actually a relatively ordinary state of life. Sometimes ordinary is the best. Really.

========================================
Same as me, eat and drink together Waiting to die. Most of them should be stacking business code

With the development of engineering, it has become a trend to use mature internal frameworks or assemble open source frameworks

Writing business code, not deeply involved in the professional field, seems to be the same no matter how many years I work After reading the high-voted answers, I was shocked! ! ! What is the state of a programmer with two or three years of experience? ? ! !

To be arrogant, I feel that with my personal efforts and two or three years of learning from Xiaobai, I can definitely kill most of these two or three years!

This reminds me of when I went home for the Chinese New Year a few years ago. All the computer students in the village had been working for two years, and I had not yet graduated from graduate school. They talked about work and writing code, and it was really like this. Just find ready-made code and apply it. They are still very restless inside and cannot study calmly. They still have a playful attitude and are more lazy, just like they didn't like to study when they were in school.

But this kind of working habit is very detrimental to the growth of small programmers

Copying and pasting is definitely inevitable at work. In an interview with Zhao Jie and Winter in a certain issue of a job recruitment agency, they also used a large amount of open source code in their work. This explains why some project managers in some answers searched on github.

The difference between small programmers and big-name C/V is that the C/V of small programmers does not want to think about solving problems. Big names already have strong technical judgment and application capabilities. Using C/V simply saves some work.

That’s wrong~~ I feel relieved to see you are like this too. ^_^