Make personal summaries and judgments on the technical product scenarios that have been watched and experienced over the years, and try not to involve controversial topics. for example, for an Internet company, technology is important or product is important. this topic makes sense.
Make personal summaries and judgments on the technical product scenarios that have been watched and experienced over the years, and try not to involve controversial topics. for example, for an Internet company, technology is important or product is important. this topic makes sense, and no one wants to convince anyone.
In addition, adding a prefix mainly targets the technical management dilemmas faced by non-technical leaders. this problem is prominent in many Internet enterprises that have transformed from traditional enterprises or personal websites.
Some of the following scenarios are faced by product managers or Boss, and readers are not familiar with them.
Such a simple requirement? Why did developers tell me how long it took?
Why can't I achieve this in my development because my peers or competitors have made it?
I made it clear, and I confirmed the development. why is it so strange for my products? It is totally different from what I want.
Offline tests are all OK, and various crashes occur when we go online. this is a strange phenomenon, which makes us unable to perform any operation activities.
I hired a big company and got a very high salary. I didn't see where it is better than a cheap programmer?
Oh, I want to refactor it again! I can't do anything for months!
Does it look like this? The programmer also has something to say.
You need to change it in three days and two days. you think my code will change 72. how much work have you done?
You said this is simple. The data structures in your system are not supported. I don't want to change it. I can't support this requirement at all. can you tell me the data structure?
You told me to do A, B, C, D, E. I did what you said. after you finish it, you said it wasn't what you wanted. the ghost knows what you want.
You just gave me this development time. I have already worked overtime to help you do things. I have implemented it and passed the test. if something goes wrong online, your business scenario may be weird, I didn't tell me where I knew it.
Every day when I have something to do, I will hold a meeting. do you know how hard it is to concentrate on my ideas? No efficiency at all. Have you ever respected my time? Do you think you can write code in five minutes at any time?
It takes an afternoon to patch the code and find a small problem. if you do not refactor your subsequent functions, none of them will be able to work smoothly and quickly. I will consider it for you. do you still blame me?
Alas, do not talk about the above shoes in disorder. I did not expect the current business to be so abnormal when designing the architecture. at that time, I was designed according to the standard popular business model. If you do not understand the essence of my architecture, you will know the restructuring. you have a problem.
Okay, stop it. the architecture topic is too big, and programmers will fight for it, which is not harmonious.
The following describes my understanding and corresponding countermeasures.
Question 1: Information asymmetry
Product personnel often think that engineers can perfectly meet all business needs by describing functional requirements and simply giving them a competitor's example. However, engineers often lack understanding of the business. Therefore, in product creation, personal understanding deviation may lead to great randomness. even if the product manager has strong control and investment, this ensures that the function implementation of the technology is consistent with the application scenario. However, it often ignores the performance requirements of the business, leading to offline OK and various online problems.
I personally think that it is necessary to allow technology to fully understand business needs and participate in business discussions. Only in this way can we deeply understand the product design objectives and key points, so as to reduce product deviations, it is inconsistent with the requirement.
Question 2: respect the time view of technicians
When will Engineers achieve the highest development efficiency? I believe that more than one person will feel this way. The period from AM to AM is time, night is quiet, no one is disturbing, and the development efficiency is the highest. We should try our best to create a non-disturbing and uninterrupted development environment. from code design to programming to testing, development requires a whole period of time to think about and implement. for example, there is a meeting at four o'clock P.M, even if it is only 10 minutes, it is no efficiency in one afternoon. At least for me, it is impossible to interrupt and continue development at any time. Many of my programming tasks were completed in the middle of the night a few years ago.
Therefore, product personnel should communicate well with technical personnel, but please try to give the entire time to engineers, such as opening a communication meeting after work in the morning to ensure the subsequent integrity, it is a recommended solution to open a communication meeting immediately after lunch, or leave it in the form of a lunch meeting to the engineers in the whole afternoon.
Question 3: idealistic sentiment
Developers often have idealistic plots, hoping that the architecture they have designed can support a wider and more sustainable application demand. Sometimes product personnel have the same idea and are too ambitious in pursuit of ambitious objectives; idealism often leads to the investment of too much useless effort into unnecessary compatibility design. In fact, with the development of business and market changes, most of the designs prepared in advance or prepared in accordance with the high-end objectives are often carried out, it is a waste of resources. In fact, the most important thing is to grasp the current market. the frequency of eliminating and updating Internet products is too fast. what is the future? there are many uncertain factors.
A typical architecture paradox is that a very ambitious architecture was designed to support more and more complex business needs, but when new demands emerged, I am sorry, the Internet is growing too fast, and new demands exceed initial expectations. then, the architecture is too complex and too large to implement.
This is often seen in well-known Internet-listed companies.
Light architecture, focus on the present, the code can be well-coupled, do not make the architecture too complex, and, in my opinion, the best design is, this allows subsequent programmers (medium level) to take over without reading documents and simply reading code.