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!
There are several types of programmers
The programmers could be divided into the following types: 1. According to the complexity of the work content, the degree of severity, and the required qualifications, they could be divided into junior programmers, intermediate programmers, and senior programmers. 2. According to the 2024 classification, there were full-stack developers, technical brothers and geeks, technical " haters ", DevOps, introverts, code influences, artificial intelligence-driven programmers, 10x developers, and ancient coders. 3. From the perspective of personal characteristics, they could be divided into genius programmers, desperate programmers, and geek programmers. " When a programmer meets a psychologist " is equally exciting. Everyone is welcome to click to read it!
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!
Can programmers check people's privacy?
Under normal circumstances, programmers couldn't directly search or obtain other people's privacy. This was to protect privacy and security. Take the password-related operations in programming as an example. Passwords were mostly stored in encrypted form. When the programmer verified the password and other operations, he could not directly check the password plaintexts. Instead, he could perform related operations through encryption comparison and other methods. On Zhihu's platform, there were protective measures for user privacy rights, and it adhered to a " zero tolerance " attitude to govern online copyright violation content, including the handling of privacy violation reports. This also meant that Zhihu would not allow programmers to check user privacy at will. However, if there was illegal hacking, it would be a different story. However, such behavior violated laws, regulations, and ethics. " When a programmer meets a psychologist " is equally exciting. Everyone is welcome to click to read it!
Ordinary people can't do programmers.
The profession of programmer indeed had a high threshold, and not everyone was qualified. This was mainly reflected in the following aspects. First of all, from the perspective of technical knowledge, programmers needed to master at least one programming language, such as Java, Python, C++, etc. This meant that they had to have a deep understanding of the programming language's grammar, data structures, algorithms, and core concepts such as object-oriented programming. For example, when dealing with some complex programming tasks, it was necessary to be familiar with the use of linked lists and tree structures in data structures, as well as the optimization of sorting algorithms and search algorithms. Moreover, it was not enough to just master the programming language. You also needed to understand database related knowledge such as MysQL, Redis, Mongodb1, etc., including common parameters, storage engine selection, index engine, table design, sql optimization, etc. As for network related knowledge, such as network protocol involved in RPC, serialization technology, etc., you also needed to have a deep understanding. Secondly, logical thinking was a necessary quality for programmers. In the process of software development, there were often complex technical problems that required programmers to quickly and accurately analyze the key problems and formulate effective solutions. For example, when checking for loopholes in a program or improving program performance, logical thinking could help programmers analyze problems in a clear manner, avoid confusion, and improve work efficiency and code quality. Furthermore, the field of programming was developing rapidly, and new techniques, framework, and tools were constantly emerging. This required programmers to have the ability to continue learning. For example, with the development of cloud computing, artificial intelligence, and other technologies, the relevant programming framework and tools were constantly updated. programmers needed to constantly learn new knowledge to keep up with the pace of industry development, or they would be easily eliminated. In addition, programmers also needed to have good communication skills and teamwork. In software development projects, you have to work closely with product managers, designers, test engineers, and other team members. In this process, it was crucial to express one's thoughts accurately and clearly, and to be able to accept the opinions of others and make appropriate adjustments. Finally, programmers needed to have a strong sense of responsibility and professional ethics. Because their work directly affected the quality of the software and user experience, they had to ensure the stability and security of the code. At the same time, they had to abide by the industry's ethics, not reveal company secrets and customer information, and not participate in illegal software development activities. " When a programmer meets a psychologist " is equally exciting. Everyone is welcome to click to read it!