It has been two months since I started my first job after graduation on July 6th.
Although I have had two internship experiences before, this one month is totally different, and it is the most unforgettable one for me. I can feel my youth fading slowly
I believe that everyone is a newcomer in just out of the campus, entering the workplace at this time, more or less have a little confused and uncertainty. During the refactoring project, I summarized some of my own feelings through the help and inspiration of the team and the mentor. I hope to share them here to help a little
1. Identify a small goal
We all worry that we don’t have direction in a new environment and that we’re not being valued. At this point, we need a small goal that can be confirmed at any time to guide a certain stage.
This small goal is best broken down into something we can understand at any time, rather than something larger that can’t be specified. For example, if our goal is to do a good job, or to get a promotion (laughs), it doesn’t help us, even though that’s what we need to do.
This small goal is a stage, according to my idea, each stage will have different goals. Goals should be in line with their current capabilities and the environment, and then in the continuous update, the overall trend will be gradually more complex and more global.
I remember the first day when I was talking to my tutor, I was asked if I had any goals. I once silence, target, I should be some, but also feel can not say, very unclear. Think for a long time can only say, is probably to enhance ability? “What are you improving?” “How do you improve?” “I was quizzed by follow-up questions. I didn’t think I was a goal-oriented person before, but now it seems completely lacking in clarity and practicality
Different people in different environments combined with their own goals are not the same. Taking myself as an example, I usually work in line with the business, so when I apply technology to complete the business, I also began to have my own understanding of the relevant business ideas, relevant optimization schemes and observation of relevant products. Current goals will include deepening the mastery of the current field and understanding the relevant business areas, while keeping my technical skills on track
2. Do the basics
I don’t know if there are any students who have the same idea as me at the beginning of the internship, always thinking that they can make great things in a short time. But then I realized that being grounded is essential, and that good code is built on background understanding and technical ability, not on castles in the air. At the same time, even if the pendant also have to complete their own corresponding responsibility, but if you want to better complete, I have a few points to share
Analyze and disassemble the problem
At the beginning, when doing a slightly complicated requirement, my thinking was always limited to the whole, thinking that I could do it at one go, but the result was that the progress was slow and there were often difficult points to analyze. At this time, it is better to spend some time to break down the complex problems first and then divide them into several steps to complete them one by one. Compared with completing a complex task, the task to be broken down is much easier. And each time a task is completed, it also provides a better environment for subsequent tasks. The whole process can be smoother and safer
Emancipate your mind and refuse to be obtuse
This tip is a subsequent version of the previous one, and it is not always smooth sailing when we want to complete an implementation, even after the segmentation. In the past, I would think of a possible plan and then start to do it. I would almost stop until the defense was broken, which often failed to produce good results and wasted time. Might as well in the discovery of unreasonable, too complex card point, out of this dilemma, to parallel or front Angle, see if there is a better way to solve, or bypass the obvious card point. Before you start, if you have more than one idea in mind, you can make some notes so that you can switch or verify each other when necessary
Basic knowledge of
Had always felt that his basic knowledge is good, but also unavoidable because of basic knowledge stepped pit. Therefore, it is recommended that every time you think of something that you don’t have a thorough knowledge of, whether it is syntax, understanding of framework APIS, or git tool classes. Can have some records, and some familiarity, in order to make their own in the development process to make low-level mistakes to minimize
Experience accumulated
I remember one development where I realized that it took me several times as long to get something done as a colleague could do it in the same amount of time. I thought to myself, worthy of being a big guy, so horrible :). Sometimes my colleagues say I just don’t have experience, but it’s not that simple. However, it is also understood that the accumulation of relevant experience in development can also greatly improve efficiency, quality, and can help to improve the height of the factor. The experience here covers a wide range, including not only the development thinking, depth and breadth of knowledge mentioned above, but also the judgment of various environments and tools, the familiarity with codes and scenes, and the communication with relevant students, etc. I think we need to deliberately absorb these, rather than just passively memorize them
3. We are not alone
Probably before most students enter the workplace, the type of code is based on individual or a few people’s ideas to decide. But now that our code is part of a larger project, things have changed. In order for our code to be useful and safe, in a sense the code that we write is the work of many of our classmates with different functions. So on the one hand, we need to enlist their help, and on the other hand, we need to take responsibility for our fellow soldiers. Friendly and efficient communication is also something I need to improve, which is as important as writing code. At the same time, with the increase of my perspective, I will also learn to think from the perspective of products, back-end, testing and other students, to view a scene and a demand in a more comprehensive way
4. We can do better
I still remember what the group leader said in the group at that time, what we want is a huge optimization. Even in our individual field, it’s not easy to do. It starts with the infrastructure of the entire team. On this basis, confirm the implementation plan through several rounds of research and discussion, and then try to execute it perfectly. In fact, we did not think before the completion of a few people can make such a good, some aspects are better than the effect of competing products, really should not be ashamed of oneself. So whether it’s getting better at a project, or whether it’s getting better at what we can do for our longer working lives, in addition to the relevant skills, we can’t afford to lose that passion and seriousness
The above are some of my superficial opinions during this period. I would be honored if I could be of help to you.