preface

I have been working in BAT outsourcing team (on-site) for more than five years. I have worked in large and medium-sized companies and served as a team leader in a small team. There’s a lot of advice and articles on the Internet about the benefits of working for a big company. Tell me about my learning experience in these years.

giant

There are plenty of great teams at Dafa, if you go in with a mindset of learning and sharing. You’ll get a lot of things you didn’t expect. Before joining the team, I embraced myself as a small shrimp with strong curiosity. When you get inside, you’ll find a lot of interesting things. The technical lights and requirements will make you feel stressed, but you will be energized. Because you will find that you learn a lot, you would not learn outside the knowledge points, and the ability to solve problems, you will consider some technical problems. Here’s what I learned:

Ability to identify problems

SSR memory leak, interface error, local forwarding, host switch, catch packet and so on.

The front-end UI is highly reducible

You’ll find that large companies require 100% UI restoration, but sometimes compatibility issues require experience.

Handle various compatibility issues

Js version compatibility, Android, iOS version compatibility. The most common is the functional compatibility of the browser version. Because some browsers still use the old kernel, you need to be compatible with the new API. For example, vuejs2.0. Internet explorer 9 or later is not recommended.

Learning the underlying source code

I deeply remember that I was immersed in the sea of code every day in the first week of my employment. Need to write a learning article every day, for example: vuEJs responsive principle, can also be said to be a team of a new assessment of it. After all, no matter how awesome you are, there has to be another channel for people to get to know you besides the interviewer.

You learn to share

  • Maybe as little as an hour, half an hour. It won’t bring you much knowledge, but it will definitely impress you, and after you share it, you’ll learn more. You’ll be interested in it.
  • The courage to speak up gradually. You’ll learn to write nice powerpoint presentations, Markdowns, mind maps, and you’ll take what you’ve learned. Share it with everyone, even if you suck at it. But there has to be a process of growth.

Product thinking

Began to slowly learn the logic of the product, how to let users get the best experience, how to guide users more accurately. The front end is the first person facing the user.

other

  • Operation and maintenance: Docker, Linux commands.
  • Multiple languages: Java, PHP, Python, GO.
  • Database: mongodb, Redis, mysql.
  • Algorithm: Leetcode brush

My personal plan, of course, is not just a front-end engineer!

In the factory

In the factory, there may only be one or two awesome people. Technical manager, technical boss, etc. They are examples for us to follow. But sometimes they are too busy. While ignoring the construction of internal team learning atmosphere. It makes you feel like you’re not learning anything here. Tell me something I learned in the factory.

Be the interviewer

Maybe because the boss is too busy. You need to be the front end interviewer. You need to control the ability of the technical team on the front end. At the very least, in my interviewing process, I must have screened at least 80% of the people.

Be the front end team leader of a technical line

There are not many people in the factory. Even if I am a team leader, THERE may be only three or five people in the front. And you still have to write code. I think everyone’s ability can be released, we should let them change, they want to change. You just need to control the quality and the scope of the possible problems. And the preparation of technical documents and so on.

Front-end learning atmosphere organizer

It is difficult to organize a front-end atmosphere. You need to lead the group to learn and share, and learn to expand your vision and improve your problem-solving skills. And because of team issues, you may not be able to touch many other things that are not in the front end scope. In particular, nGINx configuration, log viewing, and so on. Gradually share and learn to expand the vision of group members. In order to build up the learning atmosphere. So how do I create a learning atmosphere?

  • Set up internal technical documentation and technical blog. The Whisperbird and Mindoc are both good choices. The former is paid, the latter is their own internal server setup. In fact, the factory may recommend you to use the latter. After all, a server is cheaper than a paid one. Unless the technical documentation and technical atmosphere extend to other teams, then it’s time to apply!
  • As an atmosphere builder, you need to learn to share more, that’s all. You will be able to better build the atmosphere between colleagues and the learning atmosphere. As long as there is no problem with the business, according to the rhythm, we can apply for some funds for team construction.
  • The technical ability of the front end may be relatively low, and the learning time may be relatively small in ordinary times, so we should arouse everyone’s enthusiasm for learning and inquiry. Only in this way can we build a learning atmosphere.

Start-up teams (not recommended for beginners)

Not much experience, can only write some of their own encountered problems

Run, Chetu

  • If the company does not have great requirements for technology, you can completely build the business according to the technology system that you think is quite good. As long as you can convince the boss.
  • At this point, you can do a lot of things, such as deploy with Nginx, package your own code on Nginx, or write a sh script to deploy. Because there are not many rules and restrictions.
  • You can offer product ideas based on your experience. Work to make a better product.
  • Maybe if you don’t even have a UI, you have to cut and draw pictures on the side.

Busy and busy

  • Because the start-up team might be a 0-1 project. Then you’ll have to work overtime to catch up. To get the project up and running. Three months of work has shrunk to one month, or even less.
  • Your boss will be your motivator, promising you equity, a New Year’s raise, and an award for getting projects started (don’t tell me, I did get one. Very fragrant, a few months pay hand)

conclusion

It doesn’t matter whether it’s a big factory or a startup. In fact, the main or their own learning mentality and personal planning, if you just want to jump to a higher salary, you may be in a short period of time to strengthen the interview skills, consolidate their existing skills. But more should focus on their own foundation. After all, it is now facing Baidu programming. In the process of interview, I met many interviewees who were nervous, such as shaking hands, stuttering, and suddenly forgetting the common knowledge points. Maybe it’s not technical ability you lack, it’s confidence.