The first words
Have the habit of keeping a diary, from freshman start life trivial or some thoughts in his diary record, no fixed layout or format, think of what you write what, format and lax content more life also cause I seldom to sort out the contents of the diary on the blog, because is all some trivial life or some complaining words, there is no necessary to public, But today at the time of writing this diary, found a diary was written before very long, a lot of days did not even time to remember, laundry list is the status of these days, the blog is needless to say, recently all have no more than a month to finish the article, today is a busy time, after writing the diary will go in to sort out this blog post, Talk about recently busy to paralysis of the state, the whole article some partial diary.
Said to the recent work state, only busy can summarize the, basic are working full time every day, didn’t even have time to look at the news or browse the blog, that was not a bit exaggerated, task is often have been staring at a computer drive plan, wait to finish again to see the time, has been almost an hour or two later, During that time, I was so immersed in the code that I forgot to drink water and had no time to relax. Yesterday, when I was chatting with my mother, she asked me, “Why are you suddenly in a daze?” “, at that time, chatting with my eyes dull, but at that time did not really think of anything, is empty head in a daze, I replied to her work may be too busy, after home, nervous nervous some relaxation so will be in a daze, and did not talk long after she let me rest, afraid I was too tired.
The first two words
Why are you so busy?
Maybe it’s because I’m a junior programmer.
It’s a lot of work and a little time budget
During these project cycles, all progress can only be carried out according to the development plan. There must be a deadline in the plan, and these projects are all in a hurry. Therefore, under the pressure of deadline, WE can only rush the work as soon as possible. If you can’t finish it, you’ll have to work overtime to catch up.
Two points of life, the timeline is fixed: Get up at eight o ‘clock in the morning, arrived at the company start work at nine o ‘clock, at noon rest for a period of time, then work in the afternoon, at about six o ‘clock dinner, then continue to work, come home from work around 9 o ‘clock in the evening, basic is around ten o ‘clock when I get home, later will occasionally to eleven o ‘clock, just over a day, day after day, so every day.
The personnel gap cannot be made up in the short term
The most afraid of be leaking room that night when the rain, close to a period of time to catch up with the departure of tide, work up, team but attrition, a big brother has been a great help to 13 left, pressure, in the short term can arrange newcomer to the team, stress on the rest of the people, have good assignment is to subdivide again, Because modules are different, we need to get familiar with business and code, and the cost of communication with the front end and mobile end is also increasing, how to do? I had to work overtime and pull all-nighters.
Energy is constantly scattered
The next thing to say is the most difficult thing to overcome during this period of time. The workload of the project exposes the drawbacks of lack of manpower thoroughly. First, the workload increases, and second, the docking difficulty increases, which leads to the following situations:
- There’s a meeting for groups thirteen, thirteen, and three.
- Thirteen, thirteen, check this demand…
- Thirteen, thirteen, the interface is wrong! What’s going on? Check it out!
- Thirteen, thirteen, check the log, please…
- Thirteen, thirteen, the business department has a demand, help guide a data…
- Thirteen, thirteen, why isn’t the APP working?
- Thirteen, thirteen……
When I finally got these things sorted out and was ready to go on with the development, I looked up and it was time to eat.
My job is to help every day callback interface, change bug, check the log, derivative according to, of course, to the business department of derivative according to is the most hated, often a SQL to n form, write a SQL with dragon so long, very not easy to write well, but also help the data format, a basic derivative according to spend one or two hours.
Q: Why do you develop derivative data?
A: Because the people in the data center don’t talk to him. The people in the public service group don’t talk to him. I don’t want to talk to him either. But I ignore his words, he will keep bothering me, helpless face.
Think about the various scenarios above, literally, in addition to the meeting and derivative according to will not every day, every day will be some other basic works, is the cause of this situation results in thinking constantly interrupted, has just come down for a while and question, just write the function of the half to help to check the other things again, so a lot of moment are not clean, just clear, Next may be to be disturbed, hate ah, hate themselves do not have three heads and six arms, hate themselves can not alone when eight sides.
Q: Some may ask, is it all your fault? Why don’t you just help?
A: certainly not after all the problems, are not all my questions, sometimes may be the front-end friend didn’t pass the data, sometimes method to write wrong, or other small problems caused by careless, these cases will also call, because they didn’t get the desired results, and so habitual to shout A voice.
My personal opinion is that if we can quickly locate the problem, the progress of the project will be faster. If the front end or mobile end encounters the problem of improper interface adjustment, if you do not help him, he may not know where the fault is, and he will still find you later. Can not help sure ah, progress will be slow bai, and as the team is relatively old people, to help with all sorts of problems for granted, the fault of their own is kick, is not their fault to help others problem also can quicken the pace of the overall, does not necessarily make you wrong or I wrong to you, project to finish everyone happy, Why not do something that makes everyone happy?
Bugs come up all the time
The bugs I’m talking about include not only real bugs, but also fake bugs, all kinds of bugs that you come on stage and vow to beat me to death on the keyboard, along with tearing my energy apart.
Of course, there are a lot of bugs, but not all of them are particularly serious bugs. Bugs vary in size, and some minor problems are also attributed to minor bugs. There are front-end bugs, back-end bugs, server-generated bugs, and force majeure bugs. No matter what kind of bug is found, it must be found at the back end first. Why?
Maybe it’s just a habit. Then we go to locate, and then go to the corresponding colleagues to solve the problem. It may be the abnormal page display, the wrong data format of the front-end partner, the wrong forwarding of the gateway layer, the wrong code, or the abnormal service at the lower level. It’s all possible, but it starts with, “Thirteen, thirteen, look at this! Bala bala…….”
All of these are real bugs, and there’s a fake bug. What’s a fake bug?
Often, the problem is not clearly identified, and they start throwing requirements into the workflow, telling the developer that a feature is broken and can’t be used, and to look it up. Ok, the console looked at the interface, the project opened to check the corresponding function found that there was no change, and then their own operation to try to reproduce the error, the results found that everything is normal, feedback back, received a “oh ~”, light response, thick sadness. In fact, there is nothing wrong, just their own misoperation or did not confirm the problem, start to find development, this is a fake bug, this is not a waste of time, of course, but also exercise a person’s temperament, hahahahaha.
Emergency situations
In view of the work experience in the past few months, I made a simple catchphrase:
Before, there was a power outage, now there is a disk jam, the problem is erratic, thirteen upset.
The meeting is too much
Monday morning weekly meeting Tuesday requirements meeting Wednesday review meeting Thursday summary meeting Friday night summary weekly meeting occasionally a morning meeting or a party.
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 too many meetings can also make people very irritable.
The third word
The body was hollowed out
Overtime, lead to lack of sleep all night, rest bad eyes uncomfortable, the head is heavy, high load for a long time, is too much for the body, a job and supersaturation, which formed an infinite loop, and it is a very poor very poor circulation, the more busy, the body is uncomfortable, the lower the efficiency of the more uncomfortable and, in turn, may lead to work not finish, lead to work overtime, so the cycle.
You’re not just a producer of code
Is not just a programmer, not only to do the development work, even distribution of energy to take part in all kinds of meeting, to coordinate all kinds of resources, to make demand confirmation, with each side personnel to bug fixes, to check the log, side to be stalling, and product big brothers will help test the brother check interface, some developers even computer, but also help other department colleagues Good thing I can’t fix a computer, so why so tired? Because there’s so much going on.
I wrote this article for several days. Every time, I had to stop for a moment after I started writing, thinking that I would not be busy today and then started to write. After writing two sentences, I threw a bug on my face. Then busy;
Then one day I think I’ll be fine and I can clean up my blog, only to have a few more lines of error logs thrown at me.
Another day just began to write, the urgent online demand is shoved into the hand can not throw away.
This is the cycle of writing, stop, start, stop…. This article complaining finally sorted out, is a diary and blog mixed together article, record life, sigh mood.
conclusion
I have my own busy, the article is recorded some of my own experience, other people should have their own busy method, busy state is always different, complaints can be sent in the comment area, ha ha ha, nothing can stop us bragging fart happiness.
I want to touch fish!!
Recent open source projects I have maintained:
Spring Boot Open source e-commerce project (including mall terminal and background management system) : github.com/newbee-ltd/…
Spring Boot + Vue Back-end separation mall project: github.com/newbee-ltd/…
In addition to indicate the reprint/source, all for the author’s original, welcome to reprint, but without the consent of the author must retain this statement, and give the original link in the obvious position of the article page, otherwise reserve the right to pursue legal responsibility.
Thank you for watching, I am 13, the article first appeared in my public account “programmer’s Short story”.
