preface

The age of 30 is a very awkward time to be a programmer, and most companies tend to be hesitant about programmers over 30. When an interview is turned down and you feel frustrated, you will feel even more upset if you meet the company you really want to work for. And internal panic can be a lot of frustration, starting to fall into self-doubt, not sure where to go in the future, feeling confused!

❓ Why does this happen?

  • Pressure increases, powerless

Thirty years old is the age to get married, some children are estimated to have, plus parents are basically 50 or 60 years old, pressure suddenly increased, family life pressure, mortgage pressure, health pressure, children’s education pressure, support the elderly pressure. And programmer is workload originally big, often need to work overtime, a variety of things drag him, without what passion to think exclusively the thing on the job and thinking, powerless.

  • Ordinary programmers are too fungible

There are too few competent companies, leading to many programmers doing the most basic work, and it is difficult to achieve great technical improvement in the long run. The most basic work, the alternative is very strong, many programmers younger than you are enough to replace you, now that many college students graduating each year, certainly many related computer software, there are one or two years working experience of a catch a lot, in a word, older and weaker technical ability, lead to less popular in the enterprise.

  • Company cost problem

In order to reduce payroll costs, many companies tend to lay off a number of people, and people in their 30s, who are not technical staff, are often the first to be laid off.

📝 How to change

The confusion of the future, the uncertainty of their own programming work, can I do it all the time?

(1) Adjust your attitude Confusion and anxiety are normal, people of every age have their own troubles, emotional reaction means that you are still alive, and the emotion itself to promote the power of change, I believe that these problems will be solved in the end, I will find a solution.

We should first calm down to analyze the reasons for their failure in the interview, and then find corresponding solutions.

(2) Improve professional ability

As an IT practitioner in his thirties, he should be in a period of strong competitiveness in the workplace and have accumulated a lot of technical experience. However, if he still faces the problem of not finding a job, IT is most likely that he has weak professional skills and strong substitutability, so that he will have no competitive advantage in front of young programmers.

If your expertise is strong, age is not your limit. If your expertise is weak, you have fewer options. At the end of the day, we should improve our professional ability and maintain or even enhance our workplace competitiveness. If you fail to update your technology, obsolescence awaits.

Web Front-end Architect Progression path:

High order JS/TS in-depth analysis

  • Deep into stack memory and scope
  • Object-oriented OOP underlying design principles
  • Asynchronous programming
  • Event mechanism
  • ECMAScript 6
  • TypeScript

Vue underlying source code and architecture

  • Explore the Vue
  • Vue2. X source code interpretation
  • Vue2. X core frame handwriting actual combat
  • Vue3.0 source code interpretation
  • Vue3.0 of actual combat
  • Vue performance optimization for actual combat
  • Vue component library packaging actual combat

React source code and architecture

  • Explore the React
  • React Ecology and Advancements
  • React Core
  • React Advanced application scenarios

Full stack front end and engineering

  • Node.js full stack development
  • Express Framework Practices
  • Koa framework practices
  • Webpack goes further
  • Vite actual combat application
  • Mongo DB actual combat application

Cross-end applications and Hybird development

  • Wechat applets cloud development
  • uni-app
  • Taro
  • React-native hybrid application development
  • Flutter

360° full performance tuning

  • Optimization of design idea
  • Algorithms and data structures
  • Program performance optimization
  • Team collaboration

The last

Finally, summarize the experience of failing the interview, brush the interview questions, check the technical knowledge points that you do not know, and prepare for the interview again. Don’t put yourself in a state of constant anxiety and confusion.

Front-end interview information sharing:

Front-end factory interview treasure book:

More:

📢 Web front-end architect advanced route, front-end big factory interview information, front-end electronic books can be shared, join the Q skirt here:624369675Get it for free!Copy the code