At the beginning, my mentor was the most attractive man in XX. Two years later, he is still the most attractive man in XX.
preface
What do I think of my mentor? I am really very, very grateful to him, he is a smart, hard working, high eq, ambitious man, is my role model. At the beginning, when he was my mentor, he managed several people, including me. In just two years, he became a leader who managed dozens of people quickly.
His successful pace has a certain reference, every time I chat with him is enlightened. However, I am a stubborn salt fish who occasionally turns over. Some methods and opportunities I can touch with my own hands, but I resolutely let go. But that doesn’t stop me from appreciating the methodology for success, which is not such a strong word.
An opportunity to
I’m such a coffee addict that I have to grab a hot latte to wake up after my nap. On a Friday afternoon suitable for fish, I was going down to make coffee when I met my tutor who was also going down to make coffee. ‘–‘ Wait for me, come along. ‘
After two hot lattes, he went to the terrace table and chair for a chat, and I said yes (Why not Friday). After sitting down, the tutor opens his mouth to be a: “heard you want that what?”
Cough! Cough! That’s not the point. The key is what kind of wealth code I learned from talking to him this time.
Do technical skills matter most in the workplace
NO
Technical skills are secondary to most programmers in their careers, although personal development paths are divided between technical and managerial. But not to mention that few people can only do technology in the workplace with great technical ability, even if he only do technology, technical ability is still secondary, a person’s ability is weak.
An employee can move up quickly, which means that he seized the opportunity, and at the same time to seize the opportunity to convene resources, the so-called resources are either money or manpower, and then make every effort to do this thing well.
Technical ability is the icing on the cake. Technical implementation details may be important in the first three years of development, but after three years, you need to learn to look at the problem from a global perspective. Instead of focusing on technical implementation details, you need to start with what pain points the technical implementation solution can solve.
I get very thoughtful when I talk about this, because I do sometimes get into the mire of technology implementation, in short, “the pattern is small.”
Before I summarize this post in 2021, I’ll just toss around JavaScript basics or Less development documentation, or brush up on a few texts from time to time. But after I wrote the mid-year review, I felt it was time for a change. Not that the basics weren’t important, but I wanted to rack my brains to express my ideas. I hope that when I look back at my own articles after many years, it is not the same knowledge points, but my growth record, may not be perfect, may not be mature, may be very naive, but one article is my footprint 👣.
So I am grateful for watching you now, and I hope you are encouraged and grow as well.
Where is the front end engineer promotion channel
The channel is not wide
In fact, it is difficult to grasp the pain points of the whole product, the logic of the back end, and the underlying architecture when he only writes the page. You see, there are not many project managers on the front end, right?
Moving up the ladder is difficult, but not impossible. It takes a “breakthrough.”
When talking about this, I nodded my head, because it was very touching. In my two years as a front end engineer, I actually had two types of project experience: one where I just wrote the page interface, and one where the product was my own baby.
The first kind of project, in fact, I often encounter this situation, I reflect that there are many reasons for this situation:
- Let’s say the project is handed to you on a temporary basis
- For example, the value of the product is not high and there is a risk that it will be cut in half
- For example, the product is on the periphery and has no resources
- . (Additional information is welcome)
The second kind of project, I only encountered one. I started with the refactoring, although I didn’t do the actual back-end logic implementation. However, in addition to the specific backend code details, the so-called database tables, underlying architecture, deployment solution, front-end code, interaction design, project management, I have been headlong into thinking and implementation, and even sometimes to provide some constructive opinions to the product manager, have some small rights to control the direction of the product. This also shows that a front end engineer can be a good project manager when the team’s goal is to get the product right together. But there are some preconditions:
- The product has value and the possibility of sustainable development
- The product itself focuses on user experience
- . (Additional information is welcome)
How do you manage your leader up as an employee
Take the pressure off the leader, you are his confidant.
Leaders actually sometimes think of a plan is very headache and very tangled, he really want to brainstorm. So if you have an employee who can give feedback to the leader, whether it’s good or bad, you can actually benefit.
Leaders can be stressful at times, and if employees can take the pressure off their leaders, you can become their confidant. What is the role of a leader? It is to summon all kinds of resources for employees: technical support, human support, financial support, etc.
When I talk about this, I can understand why mentors are where they are now. Indeed, as an employee, it is not just about doing the tasks assigned to you by your boss. It is when you learn to think about how to do it better that you become a good employee. This may be the philosophy of how to manage your leader up. Study waste study waste ha ha ha.
How do you balance skills and chores when you become a small leader yourself
Accept that and adjust to it.
In fact, leadership has leadership skills. Many employees who have just become leaders are still used to writing code by themselves every day, which is a very bad habit. In fact, he should make a change, not to say that the leader will not touch the code, but to learn how to manage the people under him, how to train the people below to write code well.
When you become a leader, you have to deal with a lot of chores other than writing code. It depends on how well you manage your time and mindset. And he should learn to constantly reflect on and summarize his own way of working. This time it is not particularly appropriate to deal with this matter, so what is a better way to take next time?
Although AS a major soldier, I do not know anything about the management ability. But I occasionally observe my leaders, I think they are very hard, during the day there are a lot of meetings, there are a lot of problems to solve, at night when it is dark quiet sometimes have time to write code. So the higher you sit, the more pressure you’re under, and the simplest and happiest job is simply writing code.
Afterword.
After having a long talk with my tutor, I felt that I benefited a lot. Look up the watch, I still have three hours to leave work, I have to go back to fix the bug.
I feel very, very lucky to have met this mentor upon graduation. I was highly regarded when I worked for him. He took on a lot of projects THAT I was very happy with, and he was very protective of me.
Thank you very much. This post is proof.