Chapter 1
I have been in the habit of writing a diary since the first day of my freshman year. I record life trivia or some thoughts in the diary. There is no fixed layout or format. Put it on the blog, because it's all trivial life or some complaints, there is really no need to make it public, but when I was writing this diary today, I found that the last diary was actually written on April 10, and there is no running account. Time diary, you can imagine the state of the last few days, not to mention the blog, I haven’t organized the articles well for more than a month, and today I’m taking a break from my busy schedule. After writing the diary, I also organized this blog by the way. Recently, I have been so busy that I am paralyzed, and the whole article is a bit diary.
When it comes to the recent work status, it can only be summed up by being busy. Every day is basically filled with work, and there is no time to read the news or browse blogs. This statement is not an exaggeration at all. I use the computer to catch up with the progress, wait until I’m done and then check the time. It’s almost an hour or two later. During this period of time, I have been immersed in the code (to catch up with the progress), and I may even forget to drink water, and I have no time to spare at all. down time. When I got home, my condition was not very good. When I was chatting with my mother yesterday, she asked me, "Why are you suddenly stunned?" At that time, my eyes were dull when I was chatting, but it was true at that time. I didn't think about anything, but my head was empty. I might be too busy with work when I got home. When I got home, my nervous nerves relaxed a bit, so I would be in a daze. After chatting for a long time, she asked me to rest quickly, for fear that I would be too tired.
Chapter 2
As for why so busy?
Maybe because I'm a programmer.
Huge workload and small time budget
In the past month or so, several requirements have been connected to the group, one after another, and they cannot be stopped at all. During these project cycles, all progress can only be carried out according to the development plan, and the plan must have a deadline. , and these several projects have been rushed, so under the pressure of the deadline, we can only try to work as fast as possible.
Life on the front line at two o’clock is also very fixed: get up at eight in the morning, arrive at the company and start work at nine o’clock, take a break at noon, resume work in the afternoon, have dinner at around six o’clock, continue to work after that, at around nine o’clock in the evening When I get home from get off work, it’s basically around ten o’clock, and occasionally it will be eleven o’clock later. The day goes by like this, day after day, every day.
The staff gap cannot be filled in the short term
The most fearful thing is that the house leaks and it rains overnight. One of the back-end developers in the team temporarily quit because of other arrangements. The workload has increased, but the team has reduced staff. The pressure can be imagined, and new people will not be arranged in the short term. The team, the pressure is on the remaining people, the tasks that were originally assigned have to be re-divided, and because the modules are different, they have to be familiar with the business and code, and the communication costs with the front-end and mobile terminals are also increasing. What should I do? Only work overtime and all night.
energy is scattered
The next thing I want to talk about is the most difficult thing to overcome during this period of time. The workload of the project has exposed the shortcomings of the lack of manpower extremely thoroughly. First, the workload has increased, and the second is the difficulty of docking, which has led to the following Several situations:
- Thirteen, thirteen, three groups have a meeting, you come and participate...
- Thirteen, thirteen, let's take a look at this demand...
- Thirteen, thirteen, the interface reported an error! what happened? Check it out now!
- Thirteen, thirteen, help look at the log...
- Thirteen, thirteen, the business department has a need, help guide a data...
- Thirteen, thirteen, why can't the APP be used, take a look...
- Thirteen, thirteen...
When I finally dealt with these things and planned to continue the development work, I looked up and it was time for dinner.
My job every day is to help adjust interfaces, fix bugs, check logs, and import data. Of course, importing data for business departments is the most annoying thing. Often, one SQL needs to be connected to n tables, and one SQL is written so long. Once it’s written, you need to help format the data. Basically, it will take an hour or two to import the data at a time.
Q: Why do you need to import data for development?
A: Because the colleagues in the data center ignore him, the people in the public service group ignore him, and I don't want to ignore him either! But if I ignore him, he will keep annoying me, helpless face.png.
Thinking about the various scenarios above, it is no exaggeration. Except for meetings and data guides that are not available every day, the rest are basically work that must be done every day. The result of this situation is that the train of thought is constantly interrupted and just stopped. After a while, another question comes up. I just wrote half of the functions and I have to help check other things, so many times I can't get it clean, and my thinking is just clear, and then I may be disturbed. I hate it, I hate myself for not having three heads and six arms, hate You can't be alone.
Q: Some people may ask, is it all your problem? Can you not help?
A: It is definitely not all back-end problems, nor all my problems. Sometimes it may be that the data of the front-end partners is not transmitted correctly, sometimes the method is written incorrectly, or other small problems caused by carelessness. In these cases They will also be called, because they did not get the desired results, so they will habitually shout.
My personal thought is that if the problem can be quickly located, the progress of the project will be faster. If the front-end or mobile terminal encounters a situation where the interface cannot be adjusted, you may not know what the fault is if you don't help to look at it. will still find you. It’s definitely ok if you don’t help, the progress will be slowed down, and as a relatively old person in the project team, it’s natural to help deal with various problems, it’s your own fault and quickly fix it, not your own Helping others to locate the problem can also speed up the overall progress. It doesn’t have to be that you are right or I am wrong. Everyone is happy when the project ends early.
bugs appear at any time
The bugs mentioned here not only include real bugs, but also fake bugs. All kinds of bugs you sing and I will appear, vowing to shoot me to death on the keyboard, and tearing my energy to pieces along the way. fall.
Of course, although there are quite a few bugs, not all of them are particularly serious bugs. Bugs vary in size, and some minor problems are also attributed to small bugs; for bugs, there are front-end bugs, back-end bugs, and server-generated bugs. bugs, and bugs caused by force majeure. No matter what kind of bug it is, once it is discovered, it must be found on the back-end side first. Why?
Maybe it's a habit. Then we go to the location, and then find the corresponding colleagues to solve the problem. It may be that the page is displayed abnormally, or the data format of the front-end partner is wrong. It may be that the gateway layer forwarding is not set properly, or it may be us Your code is wrong, or the lower-level service you call is abnormal... These are all possible, but at the beginning, you will call out: "Thirteen, thirteen, look at it! Barabara...... "
As mentioned above, they are all real bugs, and there are also fake bugs. What are fake bugs?
Often, the problem is not confirmed clearly, and the requirements are randomly thrown into the workflow, telling the development that there is a problem with a function that cannot be used, and hurry to check. ok, look at the interface on the console, open the project, check the corresponding function and find that there is no change, and then try to reproduce the error by myself, and found that everything is normal. Deep sadness. In fact, there is nothing wrong, that is, I mishandled it or did not confirm the problem at all, so I started to look for development. This is a fake bug, which has no other effect except wasting time. Of course, it also trains a person's temperament, hahahaha.
various emergencies
In response to the experience of working in the past few months, I made a simple jingle:
There was a disconnection and power outage before, but
now the disk is full, the
problem is erratic, and
Thirteen is upset.
too many meetings
Weekly meeting on Monday morning,
demand meeting on Tuesday,
review meeting
on Wednesday, release summary meeting on Thursday, summary meeting
on Friday night,
and occasional morning or evening meeting.
In a large team, it is absolutely impossible not to have a meeting. Many things can be better coordinated and handled in a meeting, but there are too many meetings and it is very annoying.
body hollowed out
Overtime and overnight work lead to lack of sleep, poor rest, uncomfortable eyes, heavy head, long-term high load, overwhelmed body, and oversaturated work. This forms an endless cycle, and it is a very poor cycle. If you are busy, the more uncomfortable you are, the less efficient you will be, which may lead to work not being completed on time, leading to overtime, and so on.
Chapter 3
you are not just a programmer
Not only a programmer, not only to do development work, but also to allocate energy to participate in various meetings, to coordinate various resources, to confirm requirements with personnel at various ends, to fix bugs, and to check logs, while I have to argue with the big brother of the product, and at the same time help the little brother to check the interface. Some developers even help colleagues in other departments to repair computers. Fortunately, I can't repair computers, so why are you so tired? Because there are so many things.
This article has been written for several days, and every time I have to stop it shortly after I start writing, I feel that I will not be busy today and then start writing. I wrote two sentences and threw a bug in my face, yes! Then I was busy; another day I felt that I should be fine, I could organize my blog, and the result was a few lines of error logs thrown over; another day I just started writing, and the urgent online needs were stuffed into my hands and couldn’t be thrown away. This is the cycle of starting, stopping, starting, stopping... This grumbling article has finally been sorted out. It is an article that combines a diary and a blog, recording life and sighing about the state of mind.
Epilogue
First published on my personal blog , thank you for your support.
I have my own busyness, the article records all my recent experiences, others should have their own busy methods, not the same, if you have complaints, you can post in the comment area, hahaha, nothing can stop us from bragging The joy of spanking, the past and the present, are all in jokes.