Who do programmers hate the most?
There are a few types of people that programmers might hate: - Peers who did not write notes and documents would cause inconvenience to their work. - The product manager: - Changing the requirements frequently, especially halfway through, had a huge impact on the work of the programmers. - Using the boss and operations as a shield, not explaining the value of the requirements, and stuttering when the programmer asked. - Playing the role of a user and demanding the programmer based on what the user thought. - A product manager with a catchphrase like "isn't it just XXX" underestimated the difficulty of the job. - They pretended to know what they didn't know, especially product managers who knew nothing about technology but made programmers work overtime. - They didn't understand the technology and still gave orders blindly. For example, after reading a few books about product managers, they only knew empty talk. They couldn't even design the internal management background, but they liked to command programmers. Or they had more power and didn't take programmers seriously, thinking that programmers could be replaced at any time. There were also product managers who didn't understand the technology but took it for granted that code modifications were simple and blamed programmers for their low work efficiency. - An HR who offered a low salary (such as about 4800 yuan and 80% of the salary during the probation period) and thought that there were plenty of people who would do it if you didn't. - Over-management and supervision would limit their autonomy and creativity. "When a programmer meets a psychologist" is equally exciting. Everyone is welcome to click to read it!
What is the word that programmers hate the most?
According to the reference materials, programmers hated situations related to " bugs ". Although there was no specific mention of the most annoying word, the word " bug " might not be what programmers liked to see because it represented a problem with the code or program. In addition, programmers hated to write comments and documents. Words like " comment " and " document " might also be words they hated. At the same time, from the perspective of what programmers hated, frequent meetings affected programming efficiency. The word " meeting " might not be popular among programmers. " When a programmer meets a psychologist " is equally exciting. Everyone is welcome to click to read it!
Why do programmers hate ie
Internet Explorer had problems such as poor compatibility, frequent security loopholes, lack of the latest technical support, and many corporate websites needed Internet Explorer's support. Even if developers were unwilling to use it, they had to use it. This caused programmers to dislike Internet Explorer. " When a programmer meets a psychologist " is equally exciting. Everyone is welcome to click to read it!
Why do programmers hate ie
Internet Explorer had network security issues, and its inaction had led to many security loopholes. It was slow to start, easy to get stuck, the Trident publishing engine was old, and it didn't support the new web development model. This made programmers need to write more compatible code for Internet Explorer to make their web pages more beautiful. These were the reasons why programmers hated Internet Explorer. " When a programmer meets a psychologist " is equally exciting. Everyone is welcome to click to read it!
Who do programmers hate the most?
There were a few types of people that programmers hated: - A project manager who changed the requirements frequently, especially when he was forced to change the requirements halfway through. - He was a person who used his boss and operations as a shield and did not explain the value of his needs. - A person who likes to play the role of a user and use his subjective feelings to represent the user's needs. - A person who had a catchphrase like " isn't it XXX " and looked down on the work of a programmer. - They pretended to know what they didn't know, especially product managers who didn't know anything about technology and still asked programmers to work overtime. - An organizer who held meetings frequently and affected the efficiency of programming. - A manager who does not provide opportunities for learning and growth. - Someone who ignores their achievements and does not acknowledge or praise their achievements and contributions. - A planner who lets programmers do repetitive and low-challenge maintenance work for a long time. - Over-management and monitoring, limiting their autonomy and creativity. - A product manager who didn't understand technology and was still giving orders blindly. - To use the IE6 browser and still require compatibility, customers who don't understand technology but make random requests. " When a programmer meets a psychologist " is equally exciting. Everyone is welcome to click to read it!
The thing programmers hate the most to be disturbed
A programmer needed to be highly focused when working. It might take 10 - 15 minutes to recover to the previous programming state after being disturbed. If he was disturbed during the recovery state, the damage would be even greater. The disturbances that they hated the most could come from many aspects: First, they were disturbed by colleagues, bosses, clients, and other people, which would interrupt their thinking and affect their work efficiency; Second, they were assigned too many tasks unreasonably or set unreasonable deadline, which disrupted the rhythm of work and increased stress; Third, they took over code that lacked annotations, documents, and messy structure. When fixing problems, they needed to spend a lot of effort to sort out the logic, which could also be regarded as a kind of disturbance. Fourth, they received a lot of harassing calls and text messages on their phones, which affected their focus on work. It was also a kind of annoying interruption. " When a programmer meets a psychologist " is equally exciting. Everyone is welcome to click to read it!
Do programmers hate being disturbed the most?
The programmer didn't hate the person who was disturbed, but the fact that he was disturbed. Because programmers needed to be highly focused on their work, it would take them 10 - 15 minutes or even longer to recover to their previous programming state once they were disturbed. If he was disturbed again while he was recovering, the negative effects would be even greater. Only one-tenth of the programmers could return to their previous train of thought within a minute when they were interrupted while modifying the program function. Moreover, programmers could only get two hours of undisturbed time in a day, so they were very eager for a quiet working environment to ensure their work efficiency. " When a programmer meets a psychologist " is equally exciting. Everyone is welcome to click to read it!
Who are the two types of people that programmers hate the most?
According to the data, programmers might hate the following two types of people: First, some product managers, such as those who frequently change requirements, use the boss and operations as shields, pretend to be users, have the catchphrase " isn't it XXX ", pretend to know what they don't know, command blindly without understanding the technology, and look at the technology simplistically; Second, they used the IE6 browser and were unwilling to change the browser, so that the programmers could adapt to it. " When a programmer meets a psychologist " is equally exciting. Everyone is welcome to click to read it!
Is there a difference between programmers and programmers?
There was a difference. Sometimes, a programmer was just a single program related worker, while a programmer referred to a professional who was engaged in program development and program maintenance. The scope was broader. Generally, programmers were divided into programmers and programmers, so coders (comparable to programmers) were only one type of programmers. From the perspective of education, experience requirements, and job content, programmers might have work experience requirements related to specific industries (such as the glasses industry) and be proficient in using specific software programming, while programmers were more focused on writing software in mainstream computer languages. They might involve more domain knowledge, algorithm processing, etc., and might focus on a specific field or know more types of systems. In some cases, the scope of knowledge and professionalism required of a programmer were higher. "When a programmer meets a psychologist" is equally exciting. Everyone is welcome to click to read it!
Will programmers be replaced?
There were currently two views. One view was that programmers could be replaced. With the development of AI, Devin, which claimed to be able to handle the entire development project end-to-end, had made significant progress in automated programming and self-solving problems. It could solve some programming related problems independently, and its efficiency and knowledge far exceeded that of ordinary programmers. It could complete tasks such as building network applications, finding and repairing program code problems, and so on. Coupled with the emergence of a large number of AI programming tools, some people believed that the work of programmers could be replaced by large models, just like foreign language translation. It was even predicted that the number of programmers would be greatly reduced in 10 years, and only 10% would be required to do review work. Another view was that programmers would not be replaced. This was because the job of a programmer was not just to write code. More importantly, it was to transform real-world needs into abstract models (modeling) and to repeatedly maintain code assets. In actual projects, most of the time spent by programmers was spent on tuning, checking problems, locating problems, fixing bugs, communicating with the demand side, determining agreements, and so on. The actual time spent on writing code was very small, and these AIs were difficult to completely replace. For example, although Huawei had a precedent for automatically generating code, it only completed the subsequent code work after the programmer had compiled the flow chart and framework. Moreover, even if some jobs could be replaced by AI, new jobs would be created, such as a "new generation of programmers" who had programming thinking and knew how to use AI tools efficiently. "When a programmer meets a psychologist" is equally exciting. Everyone is welcome to click to read it!