Recently, I began to think about some problems. As a technical person, especially a front-end technical person, and a technical person who has done front-end development for four years, I began to feel confused and uneasy in the last six months. The confusion comes from not knowing how to further improve myself, knowing that I have shortcomings but not knowing from what aspects to improve myself. The problem lies in that the new people around are getting younger and younger. People of the same age either have good skills and go to a better platform, or they can do business and management easily and become a project leader. And I still seem to be stagnating. I believe that as a normal person, everyone’s intelligence level is not too different, and my basic quality is not bad, so why others are constantly improving, but I still seem to be stuck in the same place, writing some irrelevant business code.

I believe that everyone has a different state of mind at different stages of life, and faces different problems at different stages. I also believe that everyone has the experience of overcoming adversity and finally reaching our goals. So I think this is my current bottleneck, the key is to find the problem, AND I believe I can overcome it.

Some of my thoughts

Organize the front-end knowledge system

To be a leader, continuous learning is the most basic quality requirement. If you can’t do this, you can only be overwhelmed by the constantly changing technology. But learning is just an action, how can you learn? That’s the real problem, and that’s my problem right now. The characteristics of front-end knowledge, MY summary is messy, can also be said to involve a wide range of front-end. If you don’t have a good knowledge structure to connect these knowledge, it is just like putting furniture in the house at random, and the house will be filled up in a short time. The key is to use it, and it is particularly troublesome to rumble through it, and many things are easily forgotten.

People tend to think in a linear way, and it is easier to remember and sort out the things that need to be remembered. So I think it is very important to form my own knowledge system. If the front-end knowledge is a book, this step is equivalent to summarizing the chapter catalog first. For the knowledge learned later, we can put it in the corresponding catalog. When we want to obtain a certain knowledge point, we can find the corresponding catalog chapter.

So the first step is to organize a list of front-end knowledge for yourself. This is something I’ve done before but haven’t followed through on. With the system, but also constantly put things into it, this is the original intention of sorting out the knowledge system. There is no point in sorting it out without enriching it.

Business thinking

I seem to be a newcomer to the business. To be honest, I really started to pay attention to what my product is about a year ago (I mean the internal business logic of the product). I also believe that many people are purely writing business code, focusing on how to implement functions with the code. But this is not enough, and this is my present is insufficient, will only write business code is hard to walk, understand business, understand the requirements, understand the product’s internal logic and associated can do to look up into the road, so we know the direction, where to go, where to go is better, where to go faster, and at the same time can also be found as soon as possible is insufficient and unreasonable, timely communication with the product, We all know that the lowest-cost phase of software development is in the requirements review phase, where the cost of modification is much lower than rework and patching later.

My superficial understanding of the business is to clarify the ins and outs and know the details clearly. Attend requirement review before, PM will give to our product documentation in advance, this is the first entry, we understand the business we need to read the requirements document in advance, as developers understand the details of the requirements, the need to be marked in advance are not clear, in a requirements review can bring up the discussion, and get the answer, at legacy, I also need to follow up and discuss with PM further.

For the products we develop, we also need to draw the structure diagram of the products to help us to have a visual understanding. For example, our products are often composed of different modules, and how the modules relate to each other, how they depend on each other, how they flow and so on can be drawn in the form of flow charts. That’s the same idea: structure first, details later, helps us understand the meaning of the business from a higher perspective.

These are some of my superficial knowledge, and also the way I will continue to practice thinking.

Keep an open mind and keep writing tech blogs

Due to personal personality, I am an introvert, without an open mind. I used to keep blogging for a while, but I gradually gave it up because I thought I was not good at writing, which is also a big problem for me. There are also colleagues who have been writing blogs for several years. According to my observation of them, at least their skills are not bad.

Here are my reasons and reflections on why I didn’t stick it out:

  • Feel a lot of things others have written countless times, their own to write no meaning, because the online similar articles a lot of search. I think there are a lot of people have the same idea with me, but this is really wrong, sometimes write what really is not important, important is thinking process, the knowledge points, after does not mean you ever thought about other people’s thinking, writing articles to see article is completely different, just like now I write this blog, I am in the process of writing is totally immersed among them, the brain rapid operation, Fingers are rapidly tapping on the keyboard, which is a positive feedback to memory and thinking logic. When we learn, sort out, and express and output this knowledge point with our own thinking and language, it is completely different from reading other people’s articles.

  • No one read, no one read the written articles, this should be the biggest blow to the people who write articles, now I also want to understand, first of all, articles are written for their own reading, is their own thinking process, is their own knowledge sorting, we are our own readers, this is our own accumulation. Second of all, it’s not that important to be honest. But I believe that when you write something that provides value to others it will be read, liked, and discussed.

Finally, I would like to say that you should not write articles just for others to read. I think the most important essence of blogging is to summarize yourself and record your learning process. This is the most important.

Balance your life, use your phone less and exercise more

Finally, I want to talk about the balance of life. In the past year, I have been suffering from gastroenteropathy, both under colonoscopy and under gastroscopy. I have been taking medicine for more than a year, but no improvement has been seen. It’s been a little better lately. What I want to say is that we work to live, work hard to live a better life, the premise of a good life is to have a good body. Due to work, programmers are generally in a state of sub-health, usually heavy work, it is easy to let us give up the attention to the body. Here I would like to take my colleague as an example (there are too many excellent people around me, not only outstanding people in work, but also outstanding people in life). Some of them insist on fitness, some swim, some run. When I observe their state in daily life, they are basically energetic. Everyone is basically working the same hours, the workload is about the same, why do others have time to exercise. Later I learned that some people exercise almost exclusively at 6 or 7 am. So say want to do things, how can squeeze out time.

I think a lot of people come home after a long day and just lie down, play with their phones, and swipe tiktok. There is nothing wrong with entertainment, but excessive entertainment is an indulgence to oneself, which is what I want to warn myself.

Balance your life, use your phone less and exercise more.

The last

Technical people should have a sense of crisis, self-drive, and continuous progress. Although this is not the inherent attributes of technical people, but in this way we can go further, go better.

Eat this bowl of rice, we must take our bowls and chopsticks. Encourage with everyone