cute programmer

In " A programmer is so cute," Lu Li wanted to divorce Jiang Yicheng. Although the miscarriage was a fuse, the main reason was that the relationship between Jiang Yicheng and Riemann made Lu Li give up completely. Lu Li had seen Jiang Yicheng and Riemann meet in private many times. She misunderstood that Jiang Yicheng's old relationship was unforgettable. Moreover, Jiang Yicheng often hurt Lu Li's heart unintentionally without knowing it. These factors added up, making Lu Li feel that her love was humble and incomplete. In the end, she decided to divorce. " When a programmer meets a psychologist " is equally exciting. Everyone is welcome to click to read it!

In the professional environment of a programmer, drinking was not necessary. A programmer mainly relied on technical skills to solve logical problems, such as writing code and dealing with bugs. It had little to do with drinking and toasting. Their professional dignity lay in the code in their hands, not socializing at the table. A programmer who relied on skills for a living didn't need toasts to survive in the workplace, nor did he need to rely on drinking to build connections to obtain resources. Moreover, drinking and socializing was inefficient for programmers. It would waste time that could have been used to write code or solve technical problems. At the same time, drinking would hurt the body. Drinking and socializing could also consume the programmer's self-esteem based on technical value. However, from a leisure point of view, programmers could also drink alcohol, but it was not necessarily related to their profession. " When a programmer meets a psychologist " is equally exciting. Everyone is welcome to click to read it!

In " A programmer is so cute," Lu Li first went to Chongqing after his divorce and then flew overseas. According to netizens, Lu Li went abroad alone to give birth to a child and returned with the baby two years later. " When a programmer meets a psychologist " is equally exciting. Everyone is welcome to click to read it!

Based on the information provided," The programmer is so cute that he wants a divorce ", it was impossible to know the exact reason for the divorce. However, in general, divorce could be due to many factors. Generally speaking, the views of both husband and wife are inconsistent. For example, one party is proactive and the other party is content with the status quo, or the family concept is different. For example, there are differences in views on family matters such as housework and child-rearing, which may lead to the accumulation of contradictions and lead to divorce. Financial factors could not be ignored, such as family financial pressure, conflicts in debt, income and expenditure, etc., which could lead to divorce. In addition, couples living in different places for a long time, gradually alienating their feelings, or one party's needs in the marriage relationship, such as care, respect, and understanding, may also lead to the decision to divorce. In China, if a programmer wanted a divorce, according to the Civil Code of the People's Republic of China, there were divorce by agreement and divorce by lawsuit. The divorce procedures and legal consequences were stipulated accordingly. " When a programmer meets a psychologist " is equally exciting. Everyone is welcome to click to read it!

Lu Li's child was Jiang Yicheng's. Although Lu Li had deliberately lied to Jiang Yicheng that the child was Lu Jingwen's to test him, the child was actually Jiang Yicheng's. " When a programmer meets a psychologist " is equally exciting. Everyone is welcome to click to read it!

In " A programmer is so cute," Jiang Yicheng's ex-girlfriend was Riemann. " When a programmer meets a psychologist " is equally exciting. Everyone is welcome to click to read it!

In " A programmer is so cute," the male and female leads divorced. Lu Li had seen Jiang Yicheng and Riemann having an ambiguous relationship. She had seen them meet in private several times. She thought that Jiang Yicheng would never forget his old love and had completely given up on him. Thus, she filed for divorce and left Jiang Yicheng's company. After that, Lu Li first went to Chongqing and then flew overseas. He gave birth to the child alone and returned with the baby two years later. " When a programmer meets a psychologist " is equally exciting. Everyone is welcome to click to read it!

There were good and bad things for programmers to find a programmer's girlfriend. On the bright side, both of them worked as programmers and might have similar thinking patterns. They would be able to communicate more smoothly in terms of technology, such as in-depth discussion and mutual inspiration for new programming languages, algorithms, or technical architecture. Moreover, due to the similar nature of their work, they would understand each other's work pressure, work rhythm, and overtime needs better. However, there were also disadvantages. For example, as shown in some cases, once there was a conflict, they might do more extreme actions, such as deleting the other party's code, because both parties had the ability to manipulate the code. Moreover, if there was a technical gap between the two parties or if one party needed the other party's guidance many times but did not learn it, it might cause conflicts. " When a programmer meets a psychologist " is equally exciting. Everyone is welcome to click to read it!

The article " Ten Levels of a programmer " was not written by a novelist but by a programmer. As a programmer, he paid close attention to the life, work, and career development of programmers, hoping to help more people by sharing his experience and opinions. Although this article was not written by a novelist, it still has a certain literary value because it describes the life and professional characteristics of programmers and shows the passion of programmers for technology and innovation.

The working state of a programmer included many aspects. In the initial stages of the project, it was necessary to understand the code architecture of the project, which could be a painful process, especially when taking over a large amount of code from others. It was necessary to sort out the logical context against the requirements document (PrD) and comments. In terms of daily work processes, taking full-stack engineers as an example, they would arrive at the company at around 9 a.m. and might spend 20 - 30 minutes eating breakfast. After arriving at the work station at 9:30 a.m., they would do some preparatory work, such as tidying up the table, washing cups, pouring water, turning on the computer, browsing the news, or looking at stocks. At 10 o'clock, they started working. If they were responsible for the requirements together with the manager, they might spend an hour and a half discussing technical solutions, such as database table structure, code architecture, catalog planning, interface planning, time schedule, and other designs. He went downstairs for dinner at around 11:30 and started work at 1:00 p. m. He might not be fully awake yet and would spend 30 minutes to an hour scrolling through information or interacting with netizens. At 2 o'clock, he entered work mode and started writing code, such as the definition of the interface, the design of the business model, and the definition of the class. In terms of code related operations, in the early stages of development, after the code was debugged, a code review would be conducted before the official release. Usually, senior programmers in the company would be invited to form a review team to review the final code and check if it was in compliance with the specifications. However, this step was relatively late in the development process and consumed energy. Now, they could also use the big model to review the code. The big model could read the internal development specifications of the enterprise and review the code based on this, mark out the violation of the regulations and make suggestions for correction. The programmer could hand the code to the big model for mass review after work, and the next day at work, they could make suggestions for correction. In addition, programmers would face many situations at work, such as maintaining old code, solving bugs, dealing with unclear requirements or frequent changes, dealing with front-end and back-end coordination problems, dealing with sudden computer situations (such as blue screens), etc. There would also be work related to project delivery, such as demonstrating, showing the project to investors, and officially releasing it. From the perspective of long-term career development, programmers who wanted to work until they were 70 years old needed to persist in living until they were 70 years old, avoid over-consuming themselves (to sleep early and wake up early, and not stay up late unless there was a special job requirement), continue to learn to update their skills, maintain enthusiasm for technical exploration to avoid boredom, and try not to enter management. "When a programmer meets a psychologist" is equally exciting. Everyone is welcome to click to read it!