Introduction
Through the seven previous blogs, I shared my experience in the project optimization process. Today, as a summary, I will talk about my experience as a teamleader, problems encountered in project management and solutions experience!
Body Question 1: How do teams communicate? A good development team should first create a good development environment and have good communication and interaction between teams. Sometimes the requirements for Phase I project development are not very clear, we need to confirm while working. At this time, we need frequent and active communication between teams. The initial model should be actively evaluated and discussed. Otherwise, the products that have worked hard for a few days will not meet the requirements, call back and redo it. This not only affects the developer's mood, but also affects the development progress. Conclusion: teamleader should be good at communication and be able to communicate in a timely manner!
Question 2: I cannot understand English documents. Because the application technology is relatively high-end, I found that most of the materials on the Internet are in English, and there are too few translated Chinese documents, at this time, I really felt that "books are used to hate less", and my English was too bad. The translation may not mean anything. No way, I can only ask a friend, which is especially troublesome and time-consuming. Conclusion: English is really important. It's time to start learning today!
Question 3: We have a senior "architect" who has accepted our project and has a high requirement on the humanistic design concept of the project, here are some of our problems: 1. for web projects, the image size cannot be too large. In fact, it should be said that the size of the entire page cannot be too large. Here I think it should not exceed 300 kb. If it is too large, loading too slowly may be unacceptable to all users, after all, everyone's time is very precious.
Our problem is that there is a background image that reaches 400 Kb. After the project function is developed, I also found this problem because I have been very concerned about Web performance, so I immediately optimized the image, from 400 K to 110 K, but unfortunately, we naturally think that he should do the test in the test environment, and he did not think about it, he went to another environment for testing, and I didn't synchronize the change to two environments. So he found this problem and thought we were very unprofessional.
2. charset settings of web pages are very important
If your website involves multiple languages, you need to set a character set for the webpage to Prevent Users From seeing garbled characters in different countries.
The method is simple, but if someone finds this problem without setting it, others will think that you are not professional.
<Meta http-equiv = "Content-Type" content = "text/html; charset = UTF-8"/>
3. Versions of third-party components
Third-party components I refer to here refer to components developed by others, such as jquery and easyui. However, some people may pay great attention to the version of the referenced components, for example, jquery prefers to reference the latest version in your project, because things are always improving, and the new version may have more advantages. As for this, you can think of it as an alternative. Maybe you can list n kinds of disagree. At least I think it is enough, but we need to follow the requirements of the company's architecture, otherwise, the final project launch will be affected.
Conclusion: you do not pay attention to the details, professional personnel, or even customers will think that you are not professional enough.
Question 4: teamleader needs more time to check Project Quality
The project quality mentioned here includes the following aspects:
1. Project Progress
Whether or not there is a development progress as expected, and once the deviation from the general direction, it will be more and more controlled in the future.
2. Quality of each function completion
Although there is no problem in terms of functions, there may be some problems in the technical implementation methods, which may bring potential risks for future reconstruction. We can't say that we can complete the function. We need to consider the maintainability and scalability of your code in a certain program. For example, the project was successfully delivered in the first phase. When the customer proposes some changes later, it takes a lot of time to complete the code because our code is too scalable, customers will think that their costs are too high and our team's efficiency is too low.
3. It takes time to review from the entire technical perspective
For example, with my own experience, I also found that the background image is too large, but because I also have a large number of business function coding tasks, therefore, the problem was found late, so that the architect found the problem. Conclusion: teamleader cannot spend most of its time on specific business functions. Therefore, it needs to focus more on project progress, quality, overall architecture, and customer communication.
Question 5: if you learn to solve your own problems, some people will say, isn't it a waste of time, but what I want to express is that sometimes someone else can't help you with some problems, or if your company cannot provide you with real-time resource help, if you want to make the project go online smoothly, you need to find a solution to the problems you are not good. For example, (1) We need to optimize the image by ourselves.
In general, there will be an artist in each project. For example, if the background image of the page she designed is too large, she needs to optimize it herself, but if the artist works in other projects at this time, if you cannot provide immediate help for you, you need to optimize it yourself. (2) teamleader needs to design a project prototype
This is done by product managers in some companies, but if there is no product manager, teamleader is the product manager. The project prototype needs to be designed by yourself. Conclusion: problems that are good at should be solved, and those that are not good at should also be solved. So far, the optimization experience in the XXX project has been shared! Finally, I would like to emphasize the humanistic idea of software: software design must be user-oriented from the perspective of users. The closer it gets to users' habits, the higher the software affinity, the more popular the software is!
