Programmer August 2024 has a total of 3 updates:
1.July 2024 Articles at a Glance
2.《Programming from the Ground Up》Reading Notes：p95-p102
3.《Programming from the Ground Up》Reading Notes：p103-p116
August is a bad month for myself, two projects to catch up, from the beginning of the month to the end of the month. All the way trembling, like walking on thin ice, but finally rushed to the end of the month successfully completed, a little can breathe a sigh of relief. Looking back now, this month has helplessness, deficiencies, and relief.
Helplessness. Some project managers, may not care about what the difficulty of the project, only concerned about the progress of the project. Then there will be such a situation: managers keep asking questions, keep urging the progress - 1. this requirement to give the development of a time limit. 2. the time given to the time is up, it will continue to ask: this requirement is completed? If it is completed, they will let themselves give the next requirement development time. If not completed, will ask why can not be completed on time, how to solve the problem, when to complete? A constant stream of questions are trying to throw themselves at you. This is a poor way to manage because asking so many questions as a manager doesn't actually help solve the problem. At the same time, it also increases the tension of the whole project, and in a tense atmosphere, it is a bit difficult to do a good project quickly.
There are two places that can be improved: first, dismantling the demand. The process of doing things, the practice of estimating the time limit is not a problem, the problem is that when the person doing the work can not be done, the need to do is to dismantle the demand, talk about the need to split smaller, the time limit of the minimum granularity of 1 day, to split to the person doing the work can be accomplished until the end. Instead of always asking why it's not done on time? When can be completed? Second, participate in the project. Actual participation in the project in order to better understand the progress of the project is what, where the difficulty, that is, we usually say "pair programming", rather than as a bystander.
Insufficient. When developing applications for machines that do not support the secs/gem protocol, I found that the pyautogui and ctypes packages were used, and I was not familiar with the use of these two packages because I had not prepared for them. The reason why I didn't prepare is that I really don't want to participate in the development of this kind of machine that doesn't support secs/gem protocol. Secondly, I thought that each project would be carried out on a normal schedule and I would prepare then. Looking back now, this is a bit of a fluke, obviously in the previous has been encountered, but because of personal likes and dislikes do not go further to understand, here do not do well, need to be corrected.
Comfort. In this month, get along with customers harmoniously, which is the most gratifying point for me. Most of the customers are young people, positive attitude, willing to learn, the courage to correct. Because of the early stage is not involved in the development of their own, naturally there are a lot of do not understand, do not understand the problem, customers are able to patiently answer, and find ways to work together to solve a demand. For me, this makes me very pleased, these are very important things. The customer's positivity, patience, friendliness, and understanding gave me confidence, energy, and allowed me to rise to the occasion even when things got tough. I am grateful that I have met such people and I will continue to correct myself and move closer to them to become like them.
Welcome to search and follow: programmers (a_codists)