Let me briefly explain the background first. An unknown 985 undergraduate and master graduated in 2017 and joined Byte. He was ruthlessly laid off in the name of "staff optimization". After that, he moved to Youzan and has been engaged in software testing. No internship experience before, it is considered to be 5 years of work experience.
In the past 5 years, I completed a promotion, changed companies, had happy and contented times, and also had days of confusion and struggle, but it was a smooth transition from a rookie in the workplace to a senior paddler.
In this process, I have summed up some practical experiences, some of which I learned by myself, and some of which I learned from communicating with others. I would like to share them with you here.
If you want to learn automated testing, here I recommend a set of videos for you. This video can be said to be the first interface automation testing tutorial on the entire network at station B. At the same time, the number of online users has reached 1,000, and there are notes to collect and various Lu Dashen Technical Exchange: Click on the card at the bottom of the article
https://www.bilibili.com/video/BV17p4y1B77x/?spm_id_from=333.337.search-card.all.clickLearn to think deeply and summarize precipitation
The first thing I want to say is to learn to think deeply and summarize precipitation. This is the most important and meaningful thing in my opinion.
Let's think deeply first. In the circle of programmers, I often hear some remarks: My job has no technical content at all, and I just do a little bit every day. What can I learn from this TM? Leaving aside some ridicule and joking arguments, this It may indeed be the true thoughts of some students, at least I used to think so. Later, with the accumulation of work experience, and after discussing with some high-level students, I found that this idea was actually very wrong.
The reason for the perception that there is nothing to learn is basically the result of lazy thinking. Any seemingly inconspicuous matter, as long as you think deeply, dig a little deeper vertically or broaden horizontally, it is enough to drown in the ocean of knowledge.
Let's talk about the summary precipitation . I think this is also where most programmers are relatively lacking. They can do one thing very well just by working hard. But I almost never make abstract summaries, so that after working for several years, the knowledge I have mastered is still sporadic and unsystematic.
It is very important to make some summaries and precipitations in a timely manner. This is a process from technique to Taoism, which will allow you to see problems from a wider perspective and a higher level. When encountering the same type of problems, you can advance and solve them systematically and hierarchically according to the summarized methodology.
You can write more technical articles, share more, and force yourself to think and summarize. After all, if the article is not deep enough, everyone is embarrassed to share it publicly.
Actively learn and maintain enthusiasm for technology
An anxiety theory that has been widely spread in the Internet circle in the past two years is called the phenomenon of 35-year-old programmers. It basically means that programmers in this industry are basically waiting to be laid off when they are 35 years old. It is undeniable that the Internet industry is indeed inferior to civil servants and other institutional occupations in this respect. But the 35-year-old programmer in this question is not 35 years old in the absolute physiological sense. It should refer to those programmers who have worked for more than ten years and have worked for two or three years. The following jobs are basically living on their laurels, without taking the initiative to learn and recharge. The age of 35 is about the same as that of 25, and there is no desire for learning and growth at the age of 25. Instead, it adds many trivial matters to family life, and the salary requirements are often higher. From the perspective of enterprises, this is indeed not very competitive.
And if we actively study and maintain technical ability, knowledge reserves and working years are directly proportional, how can there be any anxiety at the age of 35? I think such big cows should be rushed by major companies, right? But learning this matter , is actually an anti-human process, which requires us to force ourselves to jump out of our comfort zone, take the initiative to learn, and maintain enthusiasm for technology. There is a saying in Didi that roughly goes that when you take the initiative to jump out of your comfort zone and feel struggling and stressed, it is often the darkness before dawn, and that is the time when you grow the fastest. On the contrary, if you feel that you are living comfortably every day and your work is just a waste of time, then you may really be boiling a frog in warm water.
During the period of just graduating, there is often a lot of free time, which is a good time to work hard to learn technology. Use this period of time to lay a solid foundation, develop good study habits, and maintain a positive learning attitude, which should benefit you for life. As for how to learn efficiently, there are many big guys on the Internet who write such method summary articles
(1) Adjust your mentality
Mentality is the key to a person's success. If you don't adjust your mentality, it is difficult to calm down and learn, especially in such an impetuous society. The status quo of most programmers is three points and one line. Tired, some older programmers will feel more anxious, and as they grow older, this anxiety will become more and more intense, so the only solution is to adjust their mentality, to be confident, young, diligent. This kind of adjustment, on the one hand, helps me to study, on the other hand, it makes me cope with the interview more calmly and smoothly.
(2) Read more bugs
Usually communicate with colleagues more, take some time to read the bugs proposed by colleagues, and understand the process of colleagues finding bugs. You can learn a lot from the experience of others finding bugs, and you can improve your own observation skills.
(3) Design your test
Whether looking for boundary values, applying combination techniques, drawing diagrams, or creating test models, it is always useful to put your thoughts into your test design. During tentative testing, consciously alternate your test plan and product learning, and keep trying to find an easier and more applicable method.
(4) Squeeze your time and make a plan
Once you make up your mind to improve yourself, no matter how busy you are, you have to squeeze in time every day, and remember not to "fish for two days and dry the net for three days". In addition, it is also necessary to make a good study plan. Review in a logical and orderly manner, first check for omissions and fill in the gaps, and then review systematically, so that you can get twice the result with half the effort and the effect will be immediate.
(5) Continue to learn technical knowledge and update your knowledge reserve
Learning should be a continuous process for everyone, after all, the times are constantly developing. If you stop learning and stand still, you will easily become the first wave to be photographed on the beach. The same is true for testers. If you want to grow and not lag behind others, you have to keep learning new knowledge and mastering new skills. Moreover, in the Internet age, the channels for obtaining knowledge are extremely rich and convenient, with video courses, open courses, and various resources. Only by keeping up with the development of the industry can we not be eliminated by the industry.
Take the initiative and communicate feedback in a timely manner
The first two are from a personal point of view. I hope that everyone can improve their personal capabilities and maintain their core competitiveness. But from the company’s point of view, the most important thing for a company to recruit employees is to let them create business value and contribute to the company. Serve.
Although there is generally a certain training system for school enrollment, in fact the company does not have the obligation to help us grow. In terms of being able to do things for the company and create value, I think the most important words are initiative, taking the initiative to undertake tasks, actively communicating, actively promoting project progress, actively coordinating resources, actively giving feedback, and actively creating influence. Power and so on.
When I first joined the company, I basically did my job well according to the tasks assigned by the leader, and then I did my own work. I almost never took the initiative to communicate with others or think of ideas that can help the development of the project. I thought it was enough to complete my job with quality and quantity, but later found that doing so was not enough. This was just the most basic requirement.
Some students' approach is that the leader only needs to synchronize the direction of what to do recently, and the following series of things basically do not need the leader to worry about. I am a leader and I like such students. A word that I often hear after joining the company is owner awareness, which probably means this.
In this process, another very important point is timely communication and feedback. If the project is not progressing smoothly, if you encounter any problems, synchronize with the leader in time. If you are not sure about the technical solution, you can discuss it with the leader. If you can’t coordinate some resources, you can ask the leader for help. Don’t have too many scruples, thinking that these will be too much trouble, the leader is actually doing it this matter.
If the project progresses smoothly and there is really no need for the leader to intervene, then it is also necessary to give timely feedback on the progress of the project and the benefits obtained, and to discuss any ideas you have, and ask the leader for suggestions on the current progress and what other areas Improvements are needed to eliminate information errors. On the one hand, doing these things is to make reasonable use of various resources of the leader. On the other hand, it can also let the leader understand his own workload and control the overall project. After all, the leader also has a leader and must report.
It may be regarded as the upward management that everyone is disgusted with. It has an internal taste, and I actually did not do well in this. But the most basic point, don’t take a task and work hard or even isolate yourself from the world. It’s been a month and you haven’t synchronized with the leader. Thinking about holding back a big move or something, that’s basically cool.
You must take the initiative. You can start by forcing yourself to speak in various public places, and one-one in time when you have questions or ideas.