What is the daily work of programmers? Can anyone share it?

As a computer-based programmer, the first thing I do when I go to the group company every day is to turn on the computer, log in to WeChat, and then start various work software (database systems, Programming software, debugging tools, etc.). Of course, some people think this is more inconvenient and do not shut down their computers immediately after getting off work the night before, so that they do not need to repeatedly open various software when they go to work the next day. As a programmer who has just started, my daily job is to type code, then test the functions myself, then fix the bugs, and then test again. This cycle lasts for a day. In fact, I spend most of my time fixing bugs. First of all, I have to figure out how to deal with it myself. If I can't solve it myself, I ask friends or netizens for help (the almighty fans can always help you solve most problems).

Of course there will be exceptions a few times a week because I will be dragged to meetings. For example, I usually go to the company before 9 o'clock, turn on my computer, then get a glass of water, soak a wolfberry, lick the pancake fruit and open the mailbox to see if there are any new emails and whether the emails are the same. If it is related to your own work, please look at the specific content of the plan at work. Then prepare quickly, take a look at the unfinished code yesterday, and continue writing. If there are no new work assignments, you can only watch things that interest you, and no one is watching you, so you can watch whatever you want. Generally, our company will have a small daily meeting in the morning, and everyone in the unit will attend it. The product operation will briefly talk about the specific distribution of the day's work, which will take ten or twenty minutes to complete. After the morning meeting, we return to our own processes, open tools like ZenTao, check our actual work plans, complete our assigned requirements according to our own work plans, and solve bugs in our projects, etc.

Then the day-to-day coding life begins. Most of the coding is routine. I have read it many times, and just complete it as required. When encountering particularly inconvenient areas, I will also ask Baidu or find Brother Gu, or communicate with colleagues to discuss how to complete it. In the afternoon, I completed the specific content of the day. I tested it myself and it was ok. I submitted it to their interface test through the environment of git and jenkins and asked the testing lady to test it to see if it can be passed. There is no proof. I came back and re-wrote it, based on it and also mentioned the branches published online. The difference from commissioned development is that there is no fixed customer. I don’t know how customers will use it. It all depends on whether many people will use it if we make it. For example, QQ, WeChat, Taobao, etc. Therefore, what requires design inspiration is generally independent research and development. In fact, it is a good idea or a good optimization algorithm.

In fact, most programmers' computers are not easy to standby, because many computers have to run data at night and cannot be interrupted. Another reason is that the programming software used by programmers is generally relatively large, and it takes a lot of time to run. In a field where time is the most efficient thing, this kind of thing is intolerable. Everyone considers that resources are wasted. Regarding the basic salary of programmers, the boss's account may be worthy of it. The programmer's goal may be more specific, how many hours per task. It’s clear how many bugs need to be resolved. The next day is to make it clear that these tasks have not been developed yet. These new tasks just need to be done by yourself. This is the scene that we often see programmers typing code with their heads down, which causes many diseases of the intervertebral disc and shoulder spine. Or how sad. Today’s new vocabulary is actually the new generation of migrant workers.