It has been three years since I became a real programmer without realizing it. Why do I say I became a real programmer, because I think that I have been wandering in front of the gate to programmers, and I have never entered it, no Knowing when to begin to realize that this is what a real programmer is.
What kind of programmer is a real programmer? This is really hard to say. After all, everyone has a field that they are good at. Just like I once asked one of my leaders and I said when will I become a java intermediate member, and my leader said that you are a java intermediate programmer when you think you are intermediate. Therefore, there is no specific definition of what constitutes a real programmer. I am just expounding what I consider a "real programmer" from a personal point of view.
First of all, I am a programmer. At least I can type code. What else is unknown for the time being. I used to be such a person. I can type code and use a few frameworks and that’s all.
Later, I entered a company and started working. I still typed code, copied, pasted, typed, copied, and pasted every day. Until one day, I found a bug due to a mistake and was led to me during the test. After I said "copy and paste with you", I really realized that work shouldn't be like this, and then I started to take my own work seriously.
Then there are bugs that keep appearing. I have to fight against all kinds of bugs every day. Some of the bugs are caused by business problems, and some are caused by my lack of understanding of technology. At this time, I began to study various error-reporting bug information. , copy and paste the wrong stack information and read it one by one, slowly understand the reason for each bug, and slowly understand the working principle of some frameworks.
Then there is the optimization of the code. The more the business is done, the bigger the project is. The unreasonable project structure will affect the operation efficiency of the business, and there are unreasonable business logic. The anti-concurrency is very poor. There are all kinds of thread safety problems, deadlock problems, and a variety of problems that were not found in the end. At this time, the problem comes again. How can I solve these problems. Fortunately, there are many powerful people around me at the time, Huawei engineers , engineers from Jingdong, etc., and some of them I don’t know where they were originally, but they are all highly educated, from Peking University, Jiaotong University, I feel a lot of pressure as a junior college, but they are very good people, usually communicate with me When I didn’t understand, he patiently explained to me and told me how to solve these problems, especially our original architect gave me a lot of help. Sometimes when I ask questions, I can’t describe them myself, but he can Understand what I mean, the progress this year is always huge, and with different people, your eyes will be different in the future. I have fully verified this truth in the future.
Later, there was a problem in the company's operation. In order to survive, many great people left. At that time, the boss of our group also left. Finally, I became the person in charge of our group. When the boss left, the company recruited our group again. Two people, these two people are the pain in my history. They were fired from the company before the probation period. To put it simply, these two people have worked longer than me. One has a child who is 11 years old. I have been working for less than two years, and they have been working for at least five years. The big brother has been here for less than two months. I assigned him a platform business and even deleted the svn project for me. I'm speechless, the old programmer made this kind of mistake... I'm sorry, after he left, I spent a week working overtime to rewrite it again. I couldn't find anyone when I scolded people, and there is another technique that should be good. But the thinking is really not on the same level. I told him that the company's business asked him to write like this, and he wrote it like that. I said that we are writing a service interface. It must be a business that exposes an interface, which is easy for others to call. When I wrote it into an interface, I told him why don't you write all the business together, but he said yes, then I crashed, and even the least one xml file reported an error, and I couldn't check it myself. I asked around, and I saw the error message clearly telling you what was wrong and that I didn't look for it. I was speechless at the time. Finally, they all left. I finally breathed a sigh of relief and dealt with various colds all day. runny nose.
Later, the company was considered to be running smoothly, and I was not particularly busy. Only then did I have time to look at the company's overall architecture model, business implementation methods, and what are the benefits of such a construction project. Also, I can finally calm down and take a good look at it. Look at the framework and see the working principle of each framework I use. Although I don't look at the source code, I should know the general working principle. During this time, my java foundation is a little solid.
When you look at the framework, you will find many common problems. If you recall the previous learning route, many problems that you did not understand will be solved. It is only during this time that you truly realize the commonality of the language you have learned. It was the real entry into the language, and it was only then that I realized that I was truly a programmer.