Hello everyone, how come this is the weekend again. Time really flies, and this fat sheep is about to be slaughtered by the pig-killing knife of the years...
Today, I won’t update the technical article. Let ’s talk about some important ideas and arrangements for a while later . Friends can also help check. After all, some problems are always raised frequently by my friends, I can't sit still, and I'm not too embarrassed.
All along, there has always been a steady stream of friends who consulted some related questions about learning routes and planning arrangements in various typical directions .
It is true that for more than a year, whether it is through articles or videos, I have communicated with a lot of friends, I found that one of the most common problems is that in fact, in the process of technology learning, the pain point is often not specific. How to learn technology, this is definitely not the most painful point. The pain point is often that many small partners do not have a macro-perceptual understanding of a certain technology stack or technical direction they want to learn. From the feedback point of view, many small partners are puzzled about the technical learning routes and specific plans of some mainstream positions (or directions).
As an opposition party who relies purely on self-study, I understand too much the feelings of my friends who need direction and line. This is almost the same as my feelings back then.
Being in it and not knowing where to go , I really feel that this is the greatest malice on the road of learning.
As you all know, I used to do communication business-related development, and I had more contact with C/C++ development related directions. Two years ago, I switched to the Internet Java back-end, so I have a little understanding of these two directions. I can probably talk about it, so I have spent a lot of time before I have sorted out the detailed learning routes and plans in these two directions:
- Java back-end development learning route and planning
- C/C++ development learning route and planning (partial background direction)
But IT company positions and job search directions are definitely more than these two. For example, many small partners often ask like:
- Front-end development learning route and planning
- Learning route and planning in the direction of big data
- Learning route and planning for testing/testing direction
- Operation and maintenance/DevOps direction learning route and planning
- Learning route and planning for embedded direction
- Linux development direction learning route and planning
- Python direction (data/algorithm) learning route and planning
- ......
Every time my friends raise questions like this, I feel helpless. Although I personally have some general understanding of the relevant direction, I am not engaged in specific aspects, and I really have no right to speak, so these have always been things I am thinking about.
then what should we do? I still don't want some friends to come here for nothing.
I thought about it, it's not impossible! Isn’t it the old face thing? Just leave it alone...
Although I don’t work in these directions myself, after thinking about it, some of my classmates and friends still have some related fields and have worked in the first line (or have worked in the first line), so I struggled and thought about it for a while. First throw a few pots and let them make up for it...
Regarding this idea, I have exchanged ideas with familiar classmates/friends. Fortunately, the students who did indeed do the relevant direction expressed their willingness to help sort out and try it first, such as front-end, big data, embedded, and testing/testing. Of course, the big guys all said that they need some time. After all, they are all very busy. I think my friends can also understand it.
Some other typical directions are also being arranged. Of course, personal resources are limited after all. If there are friends in the readers who are engaged in related fields or have related resources, they are also welcome to make suggestions and suggestions. I am very grateful.
So when the time comes to sort out the content, I will post another one in detail, and I will continue to share it with us in the later period. I hope it will be helpful to everyone.
So, stop here today, have a nice weekend, see you in the next article.
Make small but daily progress
Slower can be faster