write in front
As a code farmer who has worked for 10 years, I have witnessed the era of traffic distribution such as Baidu search and maps, and I am also experiencing the Internet + era in which the Internet drives the transformation of traditional industries. For example, takeaway is the food delivery industry transformed by the Internet. What are the differences between these two different eras, and what challenges will they bring to technology management? I would like to share with you some of my experiences over the years.
Differences between traffic distribution and Internet+
For most code farmers, Internet+ is a new thing, and many of us have come from the traditional Internet (such as traffic distribution, infrastructure, etc.). I summarize the traffic distribution products and Internet+ from products, technologies The main differences in management are as follows:
Generally speaking, in the era of traffic distribution, the products are refined, and it is easier to build barriers with technology, and the technology has a greater right to speak, so the technology management is more pure, and it is based on technology.
In the era of Internet +, I suddenly found that the world seems to have changed: products are gradually closed-loop and heavier and heavier; instead of just paying attention to the conversion rate of each link, we pay attention to the whole. For example, in a warehouse management system, page loading time is no longer an indicator, but a macro view of the cargo turnover efficiency of the entire warehouse.
You will feel that the purity of the technology is declining, the once-proud high concurrency and performance optimization seem to be useless, and the business is completely new and unknown. As a technology leader, you have come from the era of traffic distribution, and you have a deep technical imprint on your body. What pits may you and your team experience in the Internet+ era? What are the possible breakthroughs?
In the Internet+ Era, the Pit and Road of Technology Management
Next, I will share some of my own experiences. There are no high-level theories, but some lessons.
Demand is becoming more and more difficult to understand, and PK does not move
Internet+ Since you are working in an industry that you are not familiar with before, on the one hand, professional terms have increased significantly. For example, your settlement product will tell you that we are doing a "collection and payment" business, and new retail products will tell you " "Pending order", "abandoned"... a bunch of nouns that are completely confusing.
In addition to these proper nouns, the operation mode of each industry is very difficult for a newcomer to understand, and the demand for PK will also become very difficult.
For example, I once faced a very difficult demand for PK. Everyone knows that marketing is very important for food delivery, especially in the period around 2015. At that time, there was already a very complicated marketing system on the PC, and the business kept asking to move the marketing system to the sales mobile terminal. This is a huge amount of work, and it is estimated that it will take 2 months.
At first, I always disagreed with it, insisting that the input-output ratio is not cost-effective and so on. Later, by following BD (offline sales staff) to visit the business district, I learned that BD does not have any workstations. They naturally work on the move and shuttle back and forth in the business district every day. I visit different merchants every day, and the environment of the merchants is very noisy, and some have extremely poor signal in the basement, and it is basically impossible to match the marketing on the PC. BD has no choice but to write it down in a small notebook first, and go home at night to deal with it uniformly, which is very inefficient. When the competition is extremely fierce, the event will have a great impact on the merchant's order volume for half a day. Through this on-site inspection of the business district, I realized that mobile terminal configuration marketing is so important to BD, which is determined by the way the industry operates. So we immediately deployed manpower to quickly support the launch.
This kind of demand PK has experienced a lot, and slowly I summed up some experience in understanding demand under the Internet + mode:
The project is getting more and more out of rhythm
In Internet+, you are not only a newcomer, your business may also be a newcomer, or even if your business is an old driver, under the fierce offline competition, there will often be situations where you adjust while fighting. Then, as a downstream R&D student, what I feel is that the demand rhythm is very poor, there are many insertion needs, and trivial needs are also increasing. It is accompanied by the fact that there are always too many people and few people, and they are confused.
For example, I once encountered a tragic situation where there were 80 requirements lying in the demand pool, but only 3 R&D. The first reaction must be that there are not enough people, so I have to work hard to recruit people, so I interview during the day, write code at night, and see that there are 8 interviews in my calendar at most (of course, I have three interviews). As a result, a month later, few people were recruited, and the project delay problem became more serious.
At this time, I realized that going all out to recruit people will not solve the problem in the short term, and I still have to do project management honestly, mainly through two aspects, building trust externally, and sorting out the project process internally, as follows:
Through a series of internal and external management, in the end, not only did the project rhythm slowly pick up, but also the sense of trust with the business became stronger, and gradually entered a benign operation. My thoughts on this incident are:
Feeling less and less successful
In the Internet + era, everyone will complain that there are less and less technical challenges in doing things. The backend will sigh every day, and the number of users is only a few thousand. How can there be high concurrency and performance bottlenecks? Most of the work done is the addition, deletion, modification, and checking of database tables, and the business logic of if-else; the front end also complains, most of which are internal systems, which are similar. Want to play cool new technology, but the product only focuses on practicality. Even trying to use nodejs to find a test field is difficult, the back-end logic is too heavy; the test is even more complaining, and I can’t extricate myself in the whirlpool of functional testing every day.
More friends complain to you, is it worth it for me to spend so much time doing business logic? It took a lot of time for settlement people to understand account issuance, entry, and account division. When the day is not to be settled, are these students still valuable? Why don't I make an MQ service, can I still use it for another business? How much of our industry experience can be transferred?
In the past few years, these complaints and confusion have been surrounding me, and I think about the solution to the problem of achievement:
I think the first thing to do is to solve the problem of whether there are technical challenges, and then the problem of building a team atmosphere.
In addition to the promotion of capital, a very important factor in the emergence of Internet + is precisely the technology itself. For example, the services of basic applications such as mobile payment, positioning, and navigation are very mature. Even the various components used by Code Farm, such as MQ, redis, etc., have experienced a lot of experience. You may no longer need to build a cache system from scratch. I understand that the basic components for technical development are becoming more and more abundant and more powerful. Just like building a house, your bricks are much stronger than a few years ago, the performance of sand is stronger, and the raw materials are upgraded, so there is no challenge in building a house?
Certainly not, I think the technical challenges of Internet + mutual mainly come from the following aspects:
The challenge of Internet+ technology comes from the reuse and application of technology.
Take a storage system that may only have a few thousand PVs per day, is there really no technical challenge? The subsystems include merchants, orders, inventory, etc., how to combine and decouple the subsystems, and how to achieve high availability; business logic also includes permissions, logs, asynchronous export, etc., each of which needs to be refined and has a lot of attention; In addition, the Internet +'s business is in constant exploration and iteration, and the high degree of scalability is a big challenge. You can see whether a system has technical challenges or not. It has little to do with the size of the pure PV. It mainly depends on whether the business is complicated. As long as the business is complex enough, it will definitely bring many technical challenges.
For another example, is it easy to solve a takeaway merchant who does not accept orders over time? First of all, you have to analyze why the merchant does not accept the order. Maybe the message loss is not achieved. You need to improve the message arrival rate, such as using technologies such as long connection. It is also possible that the terminal has not received the push, so you need to think about when the message will be lost on the terminal. ? When Android is in the background, the push may not be received. How to keep it alive on that end, and how to evoke it when it is killed? Even if the merchant does not accept the order, it may be because the playback sound is not heard. How to determine the playback strategy, if it is interrupted by other processes, how to continue the playback, etc... You will find a problem in a scene, which will involve a lot of technical A place for constant polishing. So I understand that the technical challenges of Internet+ come from the composite application of technology.
The challenge of Internet + technology comes from using technology to liberate productivity.
As mentioned earlier, Internet + products are more concerned with closed loops, so the overall efficiency is extremely important at this time. How to use technology to improve development efficiency and solve repetitive work in daily work is becoming more and more important. For example, if the front-end is really very similar to the page, can you develop a common component library for daily use, or even make some basic templates, so that you can quickly build a page; every day, there are merchants who report incoming orders and do not respond, and communicate with merchants about problems. It's extremely cumbersome now. If a complete analysis platform can be built through full-link log reporting, problem location can be much faster. These are all things that many technologies can change the efficiency of. If you discover more in your daily work, you will definitely find a lot of things to do.
The value of Internet + technology must come from business to a large extent.
The previous article has been saying that Internet + business is very important, so the sense of value of technology must be inescapable of business. Building a sales app with thousands of DAUs may not feel a sense of accomplishment in the office, but if you follow BD to visit the business district and see how much impact your products have on offline, you will definitely have a great sense of impact. This sense of value comes from YY in the office. So be sure to actually observe and experience the product you make.
In addition, the particularity of the business will also bring you a lot of additional value. For example, many people say that the DBA of Alipay is very expensive in the DBA circle. It does not mean that the technical ability of Alipay DBA is definitely stronger than others, but more because they focus on Alipay and the like. Bank financial standards have done a lot of meticulous work, this ability is a very valuable thing.
Having talked about the sense of value of so many technologies, let’s briefly talk about the construction of team atmosphere. The atmosphere and culture must serve your current job. I have to say that Internet+ is by no means an era in which you can make money while you are in control of the traffic center. It is a very hard job. Then the culture and atmosphere construction of the Internet + technical team should be based on pragmatism. For example, if you want to praise a person's technical skills, it is not because he uses any new technology, but because he uses technology to solve a business pain point. These two orientations There are great differences; your team's technology sharing should not be about the latest technology every day, but the actual experience of who solves a problem, and how this experience can be abstractly replicated to solve a class of problems. Even if it is a discussion of new technologies, we must take a step forward and discuss where these new technologies can be used in the current situation... In one sentence, the overall team culture and atmosphere must break the blind technology worship, but be practical It seems unsexy to solve practical problems, but it is very necessary in the Internet + era.
OK, so long-winded, for the pits and roads of technology management in the Internet + era, I think it is simply summarized as the following picture:
Which are the eternal constants of technology management?
I talked a lot about the differences between technology management in the Internet+ era of traffic and traffic distribution, and how to break the situation. Finally, I would like to briefly discuss what technical management is eternal no matter how the times change?
The quality of delivery, that is, the quality of your team's projects, the stability of online services, I think is the lifeblood of things. From requirements, design and development, testing, launch, and operation and maintenance, it is necessary to spend enough effort to ensure the quality of each link and ensure service reliability. You don’t need to brag about how many new technologies your team has used and how many technical experts you have. If your product has many bugs and your online service often fails, then the technical leader is unqualified. This is your skill as a technical manager to settle down and never give up or lower your requirements.
To do management is to do service. External service products and business, internal service team. It's time to let go of the delusion that technology changes everything. Technology is essentially a tool that serves products and businesses. The way to maximize the value of yourself and your team is to make products and businesses successful. At the same time, the code farmer has a kind of arrogance. As a technical leader, on the one hand, he needs to give his teammates enough respect, and on the other hand, he serves everyone's growth with heart. A real "code farmer".
Written at the end, if I really need to summarize the technical management of Internet +, I think it is three aspects:
-
Internal strength: technology, management
-
Respect the industry, respect the industry you do, and maintain a humble learning attitude before doing any industry.
-
Service mentality, external service products and business, internal service to your team.
http://36kr.com/p/5132243.html