The topic of front-end planning was discussed in the conference, which was full of dry goods. Some points were very good. It was another day of being awakened and educated to turn over a new leaf
promotion
First, from a promotion perspective, there are several months of the year when you need to start moving up the ladder. When we start working, our goal is to make money, right? Is it technology? Is it to get to the next level in the company? It’s an end, not a goal, as Jesus said. The cause of all results is growth. What drives growth is the constant search for solutions in demand scenarios. The order is, from finish the demand, to do a good job of the demand, and then constantly from the demand to find a plan, from point to line, and then more lines to the surface, and then from the surface to the body to grow. From the business perspective, we should solve our own problems, solve the pain points of others in the team, solve the pain points of product operation and solve the pain points of the company. Finally upgrade to the big Boss. The final quantification is the dry meat of today’s harvest, which in the course of evolution is cognitive change
Landing Step 1: From done to done
The problem
- All kinds of tinkering. What if it doesn’t grow?
- When it comes to business, all you can say is what you need for the next two weeks
- Prototype need not look too seriously, anyway do not understand the time to ask the product
These three have been encountered in the work, in the passive execution, just done. If we want to continue to upgrade, this is the time to think, am I familiar with the business of the entire system? When I receive the demand of the product, why do I need to make this demand? When I don’t understand, I can ask the product why DO I need to make this demand? Can I predict what the users really need from the multiple demands, and to what extent within half a year or a year? Can we reach the point that the users are no longer the demand side, but we think farther than the users, and give us a thumbs-up when the users see the new demand coming online beyond their expectations? In the prototype section, can we look at the prototype carefully before we ask about the product? Can you point out any imperfections in the prototype? Make this requirement more perfect, rather than I do what’s on the prototype, I don’t do what’s not on the prototype, or even I don’t do what’s on the prototype?
broken
The way to break a game, from done to done, what can be done better. Traditionally, architecture and business are all business services. At this stage, what we need to do is to keep doing. The more we do, the more common problems can be found. At this time, we need to accumulate solutions
From business interface people, technical solutions, people effectiveness, quality, business understanding, communication & feedback, go from point to line to get the best out of what you’re doing. More dimensions to get things done.
Solid basic knowledge
How to do these things well, solid basic knowledge, when we eat you do not know the JS series, eat the little Red book series, combined with the scene business, do more summary, multiple requirements are used in the same set of code, extract components, with a more elegant way to call. Network, security, data structures and algorithms, framework use, principles, engineering, Webpack use and principles. For example, one of the points, like the one below, goes from point to line, line to surface to deposit the basics
Strong planning ability
When you’re in business, start planning. Code wisely. Don’t just do what your boss tells you
How to plan
When doing their own needs, ask more why, dig at least three layers, sometimes there is no need to be too strong thirst for knowledge, do one thing to the extreme, you can see more aspects, the front three magic weapons, experience, stability, efficiency.
Landing Step 2: Don’t subconsciously set boundaries
The problem
After working for a certain number of years, we can independently schedule and follow up the demand. The business performance is good, the degree of restoration is also good, and the communication is also good. Basically, nothing is too difficult to deal with. You’re in your comfort zone. Do you always do what you are supposed to do? Do you distinguish between things that are my own and things that are not my own? Do you reject things that are not my own and directly inform the demander that they are not my needs? We don’t know about other people’s business, we set boundaries for ourselves, what is mine, what is not mine, if we still do so to distinguish, then we are still executors
broken
Don’t set boundaries for yourself. Responsible both internally and externally. I can do my part perfectly, and I can do my part in foreign affairs. I should focus more on the outside to see what the operation is worried about, what the product is worried about, whether other business partners have difficulties to overcome, what is the goal of the team this year, and what technologies are needed to solve the current problems. Use your technology and understanding of the business to influence others, to help others do better, to discover what you can do differently
On the other hand, technical improvement from line to surface, specialized ability of some aspect, such as scaffolding, component library, etc. Based on the solid foundation of basic knowledge, flexible application in the project, the project structure is stable and extensible. At the same time, you need to pay attention to how you behave, be known as Mr. Reliable in other roles, and build your own personal brand
Step 3: Cross business, cross department, cross end
The problem
In their own divisional business, technology can be unified. There is another kind of failure to grow up, no one in the company is better than me, I want to quit, I want to go to a big boss team, there are big bosses can guide me, I want to worry more about technology
broken
At this time, we should look at the problem from the perspective of the team. One year later, two years later, how will our project be completed, what resources will be needed, how much time and what posture will be used to solve this problem? Cross business, cross department to solve more problems. At the same time, we should not only put our eyes on the front end, but also look at the back end. What technology do they use to solve problems? What is the system of testing? A qualified product demand, development satisfaction, customer satisfaction is how to form the demand? How do you subtract requirements?
conclusion
Our own value depends on our ability to solve problems. If you can continue to grow, it is necessary to break through their bottlenecks, step by step upgrade to play strange. Dimission is a matching behavior rather than an impulsive behavior. Figure out what you want and what you’re going to do
Talk about the front end of the conference early
About the conference: front-end early chat conference goal to become useful, understand, copy to go front conference, plan to do 12 in 2020, jointly held by the front-end early chat and nuggets, the future front-end early chat conference schedule dynamic, data download please scan the code below the public number to follow:
If you are inspired, raise your hand and send the author a thumbs up