Can programmers find other people's addresses?
Technically speaking, if a programmer had the relevant data resources and wrote a program to analyze and integrate them, it was possible to find someone else's address. For example, it was possible to check the household registration address through the ID card number (but this required legal authority and legal means such as the actual administrative division code table). However, privately inquiring about other people's addresses was an act of invading other people's privacy. If one participated in the illegal database of selling citizens 'personal information through illegal means, it was illegal and would be punished by law. Under legal circumstances, such as when a programmer in a law enforcement department was performing official duties and following relevant laws, regulations, and procedures, such an inquiry could be carried out. "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!
Can programmers find other people's information?
Without legal authorization and legitimate business needs, programmers couldn't find other people's information. Modern society placed great emphasis on privacy protection, and personal information was protected by strict laws and regulations. In an enterprise or organization, access to other people's information was usually subject to strict permission control. For example, in the database system, there was a role-based access control mechanism. If the programmer was not granted specific permission, he could not query other people's information. Even in the process of software development and data management, programmers must follow relevant privacy policies, security regulations, and ethical guidelines. They must not invade the privacy of others at will. " When a programmer meets a psychologist " is equally exciting. Everyone is welcome to click to read it!
Can programmers hack into other people's phones?
From a technical point of view, it was possible for programmers to hack into other people's phones. Hackers often hid their tracks and used complex techniques to cover up their attacks, and many of the hackers were programmers with advanced computer skills. They could use malicious software or network attacks to obtain calls, text messages, social media, and other information on the phone to monitor it. For example, they might use loopholes or malicious code in game software to invade and control mobile phones because game software is usually connected to the Internet and may have security loopholes. They could also set up fake hot spots on public Wi-Fi, let the victims connect, and then obtain information through network sniffing tools. However, hacking into other people's phones was immoral and usually illegal. " When a programmer meets a psychologist " is equally exciting. Everyone is welcome to click to read it!
Do programmers monitor other people's phones?
There were cases where programmers monitored other people's phones. Some programmers might use technology to monitor other people's phones, but this kind of behavior without the consent of others was immoral and could be illegal. For example, by inducing the other party to click on a link sent by a text message, social software, or a fake APP, a trojans program could be implanted to monitor the phone. However, under normal circumstances, most programmers would not do such illegal things. " When a programmer meets a psychologist " is equally exciting. Everyone is welcome to click to read it!
Can programmers see other people's browsing history?
The programmer couldn't see other people's browsing history. Generally speaking, everyone's personal information was private, and programmers could not check it at will. Although programmers knew more about computer programs than ordinary people, if they wanted to check other people's personal information, they could only use hackers to steal the other party's personal website to obtain information. This kind of behavior was morally and legally unacceptable. " 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!
It's hard for programmers
There were indeed many difficulties in the profession of programmers. In terms of the nature of their work, programmers needed to develop and maintain programs. They might face code logic errors in their work, and even if they checked repeatedly, it would be difficult to find the root of the problem. Moreover, as they grew older, programmers would experience a natural decline in their mental sharpness and memory. This was a big challenge for programming that required a high degree of concentration and logical thinking. From the perspective of career development, the Internet industry was developing rapidly and the work intensity was high. programmers had to constantly learn new knowledge to keep up with the development of the industry, and at the same time, they faced the pressure of promotion in the workplace. In terms of perception, although programmers were often mythical, they were actually ordinary workers. They faced professional risks such as being fired at the age of 35 (of course, age was not the only factor, young programmers could also face the risk of being fired), and they also had to deal with psychological pressure such as unrealistic expectations from the outside world. In addition, they had to find a balance between efficiency and operating habits in the use of the keyboard and mouse at work, which showed that there were many difficulties in the profession of programmers. "When a programmer meets a psychologist" is equally exciting. Everyone is welcome to click to read it!
Why do people always say that programmers are bad?
People thought programmers were bad mainly because of the following reasons: ** 1. Work pressure ** 1. ** High-intensity work ** - The work of a programmer required a high degree of concentration. Maintaining this state for a long time would bring about both physical and psychological stress. For example, when dealing with complex algorithms and checking for program faults, the brain needed to be in a state of tension for a long time. - They often face computer screens for a long time, which can easily lead to eye fatigue, headaches and other health problems. 2. ** Long hours and overtime ** - During a project, programmers often had to work long hours or even overtime. This was because the project might have an urgent delivery deadline, or there might be sudden problems in the development process that needed to be solved in time. Long-term work would affect their normal pace of life and negatively affect their health. ** 2. Professional development ** 1. ** The risk of technology becoming outdated ** - Technology was developing rapidly, and programmers had to constantly learn new skills and knowledge. If they couldn't keep up with the changes in technology, their skills would soon become outdated. For example, new programming languages and development framework were constantly emerging. If programmers couldn't master them in time, they would lose their competitiveness in the job market. 2. ** Repetitive work ** - Some programmers would face repetitive tasks, such as writing some basic code modules with similar functions. This kind of repetition easily made people feel bored and gradually lose interest in work. ** 3. Social aspects ** - Since most of their work required them to face the computer alone for a long time, it was difficult for programmers to establish close social relationships with others. A lack of social interaction can lead to social isolation, which can lead to depression and affect mental health. " 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!