Recommended requirements management method; how to quickly understand a framework; the future direction of front-end | Extremely objective point of view

Waiting for the light on the bench~~ Developers in the community, have a good weekend!

Before I knew it, the brand new section of the SegmentFault sifu community has been online for more than a month~

# Extreme Objective Focus on topics such as technical direction, programmer career development, personal growth, etc., and is committed to initiating valuable discussions and outputting valuable opinions.

In this column, we will recommend topics that have been hotly discussed in the #extreme point of view section, and select interesting viewpoints to present to you. Looking forward to our growth and progress together 🥰🥰

Today's keywords: #demand management method #framework learning #front-end future direction

Are there any recommended requirements management methods?

Topic initiator: Zhu Chenglin

I am a report analyst, and there are many business departments in the BI department of an Internet listed company. The demand is always passed on WeChat, and it is inevitable that some will be missed....
After the analysis of the report is completed, and the development is carried out, there is no way to see the progress of the development process. …
The business asked me → I asked the development → the development attacked me → I can’t attack the business. Dare to ask if you have any useful methods or tools for demand management? Otherwise I'm going to be slaughtered to death

Interesting point:

If you are a listed company, your team size should still be quite large. Does the management of development sound so rude?

It is recommended to sort out requirements management specifications clearly, and ensure that all relevant departments and roles are clearly understood.

For example, after a requirement is raised, the requirement should be reviewed, clarified, determined to be a real requirement, then prioritized, planned for iteration, assigned a person in charge and estimated man-hours, and then entered the development phase.

Specifications are the foundation, then use tools, and put the specifications on the wiki to ensure that all relevant personnel understand it. It is best to solidify some standardized processes on the tools. For example, setting requirements must be reviewed by the product manager before they can continue to flow; During the development process, if the business party suddenly changes the requirements, it needs to be re-evaluated. If the change is determined, the change information needs to be synchronized with the relevant personnel, and the impact of the iteration plan that may be caused by the change must be synchronized.

Establishing norms and solidifying processes is actually improving the information transparency of the team, ensuring that the demand value is understood, and improving the efficiency of collaborative communication.

For R&D management tools, you can look at ONES. Their demand management capabilities are quite strong. They support customization of demand attributes and workflows. You can also pay attention to the demands you create, see the status of the flow, and set reminders for some key nodes. .

———— Community User: Diva

Interesting point:

First of all, it is highly not recommended for landlords to talk about their needs in WeChat. Just imagine, how many groups are there in everyone's WeChat, and how many messages are there every day?

If you mention it in WeChat, even if it is a person, it will probably be swiped or forgotten.

Let's talk about what I used before. In the first company, we had our own reporting platform, but we used taped and Feishu the most. Of course, I have seen the recommendations of my classmates in other answers, including Zen Dao and Ones of the Sifu community. Since other tools have not been used, I will not comment.

In response to the landlord's description, I think it is obviously not enough to recommend only one or two software. After all, some things need to be solved by people. (Because I encountered a similar problem in my last company), it is recommended that the landlord and business, development, operation, and product related work together in a work gap, and hold several related meetings together to see if they can achieve certain things. convention. For example, jointly agree on one or two pieces of software to record and follow them together.

Finally, let me say something silently, usually Internet listed companies have their own sound business demand reporting platform. The landlord may wish to ask the leader, how did you do this before?

—— Community user: Qu Xiaokai

Front-end novice, ask questions, how to quickly understand a framework ?

Topic initiator: _Xiaohui o

Recently, I am learning the front end, and then I mainly watch videos and take notes.
Then add some practice or something.
I would like to ask how everyone learns a language, do they just watch the video, or do they just watch the document for practice?

There is also a framework encountered in learning a framework project. Is it directly to see the document from the beginning to the end, or to selectively view, which one is encountered?

Interesting point:

How to quickly understand a framework?
1. You are sure that you want to enter the front end, then the three Musketeers of html, js and css must be learned.
2. Among them, js is the basis of all frameworks. You can not frame, but js must be. Of course, learning js is difficult.
3. The learning method is of course: watch other people's videos first + take notes by yourself + official documents/community documents/blogs + write by yourself.
4. Learn a framework, the front-end here is divided into application framework (Angular, Vue, React,...) and UI framework (based on application framework encapsulation, for example: ant-react, Vue is too much, Angular's ng-zorro). It is recommended to read the official documents for the application framework. The UI framework does not need to read all the documents of others. When you use the project to use what components in the UI framework, go to the documents.
5. Among the three popular front-end MVVM frameworks Angular, Vue, and React, Vue and React are used more. Angular is rarely used anymore. Beginners are advised to learn Vue first, then React, and Angular may or may not be learned.
6. As for the framework source code, it is not recommended for beginners to read it. If you read it, it will greatly damage your self-confidence. When you are proficient in using it, come back and look at the source code to learn other people's ideas, coding style, etc. is the best.
7. When you decide to enter the field of code farming, the learning will always be with you. New technologies are constantly being produced. If you don't learn, you will fall behind. Not only to study at work, but also to study in free time.

———— Community User: NeverGiveUpT

Interesting point:

In fact, on this point, the opinions given by people of different heights will be different on the level.

Ordinary users can just look at the basic syntax structure, use tools to initialize the framework code, directly open the document or video, and make something.

If you want to use it well, you must learn to understand the principle of the framework and the initialization process, such as the process of starting the framework, the life cycle, the data transfer between layers, the rendering method of different data structures in the framework, and so on. These are tiny things, and it's personally hard to focus on them at the beginning before doing a project. Generally, it is learning by doing and deepening understanding. Then it is inevitable to make all kinds of seemingly low-level mistakes. These mistakes are actually the necessary process of knowledge accumulation.

What's more, for those who have obsessive-compulsive disorder in learning, they will pull out the source code to see its implementation principle, analyze its advantages and disadvantages, and then recommend it to others after finding a sense of identity.

My personal suggestion is to use it well and use it well enough. But if you want to rely on it as your main skill to eat, then you can either read the source code, or read more technical blogs to understand and learn the principles of the underlying implementation. This will help you go to the senior job interview. Of course, the use of the surface, the familiarity and mastery of the middle level are the most important, and the bottom level are those things that the interview dogs have come up with to raise the threshold.

—— Community User: Mr. Mu Chen

The future direction of the front end

Topic initiator: demon

I would like to ask the majority of netizens a question. I am a front-end developer, and I have encountered my own bottleneck. I am thinking, in the future career direction, whether to study the depth of the front-end, or learn the breadth of the back-end development, welcome everyone Friends to give an opinion, the younger brother is very grateful!

Interesting point:

1. Continue to accumulate experience in small projects.
When you have nothing to do, you can look at the source code written by others, do some local small tests, and complete it according to the general online product requirements. In this process, you can also cultivate your own product thinking and habits, and accumulate useful code. .

2. Take a long-term view.

Now that the technology is changing rapidly, why is the front-end technology developing so fast? Following the increasingly diversified needs of customers, the popularity of express delivery of large-screen mobile phones and mobile tablet computers has long been unsatisfactory with the previous technology.

3, the system of learning knowledge points.

Beginners who are a bit basic, remember to systematically learn front-end knowledge, this is the only way to deepen front-end. A single knowledge point is relatively easy to learn, but a knowledge system is difficult to build. The front-end knowledge system should include at least the following aspects: H5 core, JavaScript, VUE framework and React framework. It is estimated that most people cannot fully grasp it. So once again reminded, do not end up in the act. It is necessary to be clear about the current market demand for front-end positions: the supply of primary front-end is oversupply, and the supply of advanced front-end is less than demand. If you want to go to the next level, there is still a lot to learn.

4. Get out of your comfort zone.

After working for 1-3 years, the feeling of powerlessness brought by the bottleneck period began to gradually appear: there are only a few types of problems to be solved in the work, and the speed of absorbing new knowledge gradually slows down. As a result, a large number of people's skills improvement gradually depends on browsing forums and reading articles. As a result of being so obsessed with the status quo and losing the sense of crisis, what you gain is not work experience, but only working years and age. At this time, the biggest challenge is whether to jump out of the comfort zone, and how to smoothly transition from the principle to the source code, keeping up with the speed of technology change. This stage is very difficult. If you have seniors who often communicate and share experience, you can break through the bottleneck faster. However, it is difficult for everyone to meet reliable friends at work, let alone excellent senior leaders. At this time, the necessity has emerged. Therefore, to enhance the competitiveness of the workplace

—— Community user: Teemo looking for mushrooms

Interesting point:

First of all, ask yourself if you really like programming and front-end. The premise is that you must first understand the current industry status of front-end development. What are the directions?

If these are not clear, then enter the industry first and learn as you go. Maybe after two years, you will find that you prefer the front end (or back end), because with the increase of experience you will find that Interest is the best teacher, and interest is the reason why you really persevere in the end. Come on!

———— Community users: _AN_

---

Do their views and discussions inspire you as well? Do you have any interesting ideas that you would like to share with you?

Scan the QR code to join us, let’s communicate and grow together, waiting for you🙌🙌🙌