Introduction to is a very ordinary technical engineer. He has been working for 7 years since he graduated in 14 years. This article will share with you some truths and experiences in the workplace, hoping to inspire and help you.
Author | Baozhen
Source | Alibaba Technical Official Account
Preface
Simply introduce myself. I am a very ordinary technical engineer. I have been working for 7 years since I graduated in 14 years. Along the way, I feel very lucky to meet a lot of Bole and have taught me a lot of truth and workplace experience. In recent years, I have also interviewed many students as an interviewer. I often communicate with many candidates to share some of my own learning and growth paths. I also often share some work experience with many new recruits. Now I have summarized these experiences. It would be best if I can inspire and help students who read the article.
Ten experiences
1 Self-awareness
Many newly recruited students, especially those recruited by society, will not adapt to the new environment (perhaps colleague relations, work mode, work environment, etc.), and will gradually become confused and anxious. First of all, it is normal to have this kind of emotion. It takes a lot of courage to get out of your comfort zone and adapt to the new environment, but you don't need to magnify this emotion. The main thing is to be clear about what you come to this company and team for. In short, you must be clear about your own demands, and then look at what the team is doing up and down, what the team needs you to do, what you can do for the team, and position yourself.
2 Basic literacy
As a technical engineer, you must have the most basic pursuits and accomplishments. These things determine the lower limit of your future, including: self-driving learning, pursuit of the ultimate, ingenuity culture, one stroke to the end, ownership spirit, etc. Here are not one by one, there are also many introductions and instructions on the Internet. It was said in "Top of the Tide": First-class engineers can match 10 second-class engineers. First-class engineers are born with a sense of responsibility and curiosity. Most of them are confident but conceited. They are direct but not rude, and they do not shirk. They don't care about work boundaries and aim for the team rather than their own work tasks.
3 Growth path
There is more than one way to climb the mountain, and here we mainly talk about the growth path of points, lines and planes. When you are in charge of a small module, have you considered the design and ideas of the entire project or system; when you are in charge of a system, have you considered the design and ideas of the full-link architecture; when you make a When designing the overall architecture scheme, did you consider ROI, and did you know whether other architecture domains have similar problems? When you gradually acquire these abilities and consciousness, congratulations, you have become stronger, and you may become bald. Of course, it is also possible that you already have these abilities, but you have not appreciated your Bole, so you must seize every opportunity and do some small things to the extreme. If Bó Lè still does not find your abilities, it is also a good choice to make appropriate adjustments.
4 Define the problem
I interviewed many classmates, and helped some classmates with simple internal promotion counseling. Many classmates came up to talk about my plan, how to be effective, and the specific details. But from the perspective of other people, he doesn’t have the context, and he doesn’t know what the problem you are trying to solve, what the derivation logic is, and without these things, it’s difficult to judge the quality of your plan, and the plan. Did it really solve the problem? So knowing how to do it is important, but defining the problem is more important, and then your thoughts and derivation process. This is also often heard in the promotion field. Think about the WHY and WHAT behind the problem. Defining a problem is not to put a hat on it at will. When you become a supervisor, you are the beacon of the team. You must analyze and define the problem according to the characteristics of your own architecture domain in combination with business needs and trends.
5 Upward management
I personally feel that upward management is not a derogatory term. Many times you are doing things with your head. If you don't focus with your supervisor often, you may understand something completely different from what he thinks. In the process of implementation and landing, communicate more, focus more, and think about what kind of classmates you like as a supervisor. Of course, it’s not enough. You still have to have high-quality dialogue and input, not just think of something and ask the supervisor for communication and feedback. When you are a supervisor, you should always have one on one with the students below, listen to the ideas of the teammates, and give the teammates the opportunity to communicate.
6 independent thinking
In the online society, we will actively or passively acquire all kinds of information and knowledge, and you need to listen to it. As mentioned in the self-cognition above, we must clearly know what we want. Don't listen to the wind or rain, and be led by others to your own growth path. The same is true for technical thinking. The definition problem mentioned above is also thinking about solving the problem. In addition, when making technical solutions, many students will panic immediately after being challenged by others. The main problem is the problem to be solved. Or whether you think deeply about the phenomenon, whether you are very sure about it.
7 Summary precipitation
Summary and precipitation must be done in daily life, whether it is PPT or notes, these summary and precipitation do not have to be technical architectural ideas, but also some of their own thoughts and insights. When some students introduced their own ideas or technical solutions to others, they said a lot of content but did not focus at all and could not grasp the essence of the problem. Mainly because of two aspects, one is that you haven't really thought about it yourself, and the other is that you haven't formed an effective summary after thinking.
8 Bow into the game
Some students have jumped in their thinking and have a lot of ideas. They always like to give pointers. They feel that the design of this scheme is not good, and that the code is written wrong. But when he was really asked to solve it, he realized that many problems can't just look at the surface, and they will find a lot of details after bowing into the game. It’s not that you have ideas and it’s not good to like to give pointers, but whether you have seriously thought about this problem in a specific context. Can you give a better solution? In addition, after bowing into the game, you can't get into the details and can't extricate yourself. When many students make technical solutions, their thinking will be particularly divergent. They feel that this is not reasonable, and it seems that it is not feasible to do it like that, and they have been hesitating. I especially like the intranet signature of a classmate: all thinking is a question, and doing is the answer.
9 soft skills
The above said that basic literacy determines your lower limit, but for most ordinary people, soft skills determine your upper limit. Soft skills include but are not limited to: PPT, presentation skills, emotional intelligence, etc. Most of us are not geniuses, and we still have to collaborate with many teams and many people in the company. I remember when I was doing an architecture proposition, I heard a big man jokingly said: Inter-departmental collaboration is not necessarily a technical boundary issue. Many times you ask the other party to have a meal and exchange real ideas. Maybe the problem will be solved. Here is an extra point. The communication skills-empathy. When many students communicate, no matter who they are with, they are all a thought and tone. In fact, when facing different roles, you have to think from the perspective of the other person, how to make him more accepting of your plans and ideas.
10 Unity of Knowledge and Action
It is very important to understand a lot of truths and things. Just as you read this article and feel that there is some truth to it, but you haven't made any changes, it means you haven't read it. Knowing a lot of great principles, but still having a bad life, and talking about the same problem. The Yangming Mind School has always emphasized the unity of knowing and doing, combining one's own cognition and action, knowing and doing, and doing knowing.
Conclusion
Work is only a part of life. Take more time to exercise and read, and to spend more time with your family, let's relax. Finally, I recommend a few non-technical books: "Pyramid Principle: The Logic of Thinking, Expression and Problem Solving", "The Weapon of Thinking That McKinsey Taught Me", "The Essence of Thinking", "Diligent: How to Become a Great Person", "Seven Habits of Highly Effective People", "Deng Xiaoping Times."
Technical Open Class
"Go Language Complete Self-study Manual"
Go is a concurrent, garbage-collected, and fast-compiled language. It combines the ease of interpretation of an interpreted language, the development efficiency of a dynamically typed language, and the safety of static typing. It also intends to become a modern language that supports network and multi-core computing.
Click here learn Go language~
Copyright Statement: content of this article is contributed spontaneously by Alibaba Cloud real-name registered users, and the copyright belongs to the original author. The Alibaba Cloud Developer Community does not own its copyright and does not assume corresponding legal responsibilities. For specific rules, please refer to the "Alibaba Cloud Developer Community User Service Agreement" and the "Alibaba Cloud Developer Community Intellectual Property Protection Guidelines". If you find suspected plagiarism in this community, fill in the infringement complaint form to report it. Once verified, the community will immediately delete the suspected infringing content.
**粗体** _斜体_ [链接](http://example.com) `代码` - 列表 > 引用
。你还可以使用@
来通知其他用户。