About the guests
In the 33rd AMA, we invited Alibaba – Tao Department technology Department – Channel and D2C intelligence Team, namely F(X) Team. They are committed to the exploration and practice in the field of front-end intelligence, enabling front-end intelligence ability, releasing front-end productivity and service business innovation.
This time, they will talk with digg friends about “taobao front end”, “front end development”, “front end intelligent direction”, “career development”, “personal growth” related issues.
Select questions
1. If the front-end wants to learn the back-end knowledge, how to plan it? Learn Node or PHP, mysql or mongodb or Redis?
I suggest learning in the dimension of a project, such as trying to write a blog system from scratch with Node.js. In this process, you will encounter how to write HTTP service and database. In the process of writing, you do not need to go into depth or choose difficulties. When you’re almost done with the project and you have a pretty good idea of what you’ll need for the whole backend development, then you can think about mysql/mongodb versus Redis.
2. Should we write unit tests at the front end of a business-oriented project?
I think it depends on how you look at unit testing. First of all, I think writing unit tests itself is a Review of code. It helps you understand your code better and also exercises your ability to write testability code. If you want to grow in this area, I believe both business and technical projects need to pay attention to it.
In addition, business projects generally change a lot, and people often think that a single test written today may be useless tomorrow. I personally think that there are two problems. First, business changes quickly and the code changes greatly.
Secondly, there is a cognitive issue. Unit testing is a tool that helps us to ensure that the code delivered is of good quality. It does not say that the code delivered is tested and then rejected again.
3. How to keep learning motivated? Especially at ordinary times the job is very busy originally, how the time outside work, appreciation oneself?
So why not add value at work? For programmers, our duty is to write code, how to write code well, is very worth studying, even business code, how to write business code well, write for a long time, write easily, these are opportunities for growth. Don’t try to develop pure technology just because you see everyone else doing so.
Another recommended book: Complete Code, after reading this book, I believe you will believe that writing code itself is a craft!
4. How to advance the front end, which is equivalent to p5 to P6, and how to learn the process from P6 to P7?
This question is not easy to answer, the definition of high middle school is not easy to say. Uncle Wolf’s understanding is as follows.
P5 Elementary, with programming background and quick learning ability to solve problems.
P6 Advanced, in fact, is intermediate, the so-called independent, assisting the team, to put it bluntly, can be independently responsible for a project, but also bring new people, in charge of team building.
P7 experts, in fact, senior, can be responsible for some business, have independent views on technology, a certain direction of ability. You can bring people or not.
P8 is not among the engineers, in addition to the right, Yunqian, Chengyu, etc., are still writing code big guy.
5. Relatively few programmers enter big factories after graduation. Most programmers work in small businesses after graduation. Most of these smes do not have standardized RESEARCH and development processes, nor do they value code quality and precipitation, and their exposure to the field is relatively limited.
I am such a programmer. In the recent interview process, I encountered a problem that the project was not bright enough, not broad enough, and not deep enough (within the scope of the company’s business). Although I am trying to break this limitation, Including but not limited to buying various courses, buying various books, browsing technical forums, trying output, participating in open source projects, but still no direction. I want to ask how to break the game in this situation?
There is no r&d process in the world, but when more people use it, there is a process. Just graduated, avoid by all means is irritable, slowly put himself on hand of a thing well done, and then have problems require the solution, it is good to read some classic books (CSAPP, for example, code books), slowly feeling in a work book puts it, in a word, have a problem to solve the problem, in the process of problem solving, and learning and experience. Programming is a practical work, reading is good, but must write more code, read more code, more running code.
6. Could you recommend a book that you think is most helpful for improving yourself?
CSAPP and About Face have the greatest influence on me. One book enables me to get into the world of computer, and the other book enables me to understand how to design software for users.
7. I have been working for some time ~ is the back-end better than the front-end?
It’s better because now TS, where Nest and Angular and Java are still very much like each other, think like each other and write easier. React today is much more complex than it was in JQury’s time. There are webPack, CSS preprocessors, TS, Babel, etc to understand. Follow your heart.
8. Intelligent code generation of design draft: is this a “shallow code” way to quickly understand and access what threshold or technology is needed, or the group and team that this technology is suitable for?
At present, it is the way of low code, which improves the efficiency of code writing and is completely consistent with the design draft. The most recommended way of fast access is to read our tutorial. Pure static page, anyone can easily operate to generate. Front-end students, you can save the cost of writing CSS and HTML, there are multiple DSLS can choose to export, just write code logic. We are also currently working on ways to reduce the writing of code logic and welcome your continued attention.
Due to space reasons, this issue only extracts some of the issues. Want to see more sharp answers from F(X) Team? Click on the portal