Do programmers monitor their girlfriends 'phones?

Some programmers would monitor their girlfriends 'phones. Some programmers, out of concern for their girlfriend's loyalty, might use methods such as Root or unlock the phone to obtain access to system files, install monitoring software, and use the mobile cloud service to sync chat records to monitor the chat history, call history, location information, etc. in the girlfriend's phone. However, this kind of behavior involved moral and legal issues. It was an invasion of privacy to monitor other people's phones without the other party's consent. " When a programmer meets a psychologist " is equally exciting. Everyone is welcome to click to read it!

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!

From the many cases in the reference materials, programmers had a good side to their girlfriends. For example, in data 6, the programmer Xiao An would give half of his monthly income of about 5,000 yuan to his girlfriend as living expenses. This showed that he had made financial contributions to his girlfriend and wanted to take care of her. However, the characteristics of a programmer's work might also have an impact on relationships. As programmers worked overtime, it might cause them to spend less time with their girlfriends. For example, it was normal for programmers in the Internet industry to work overtime, which might affect their time with their girlfriends to a certain extent. In addition, in data 3, the relationship between the developer and the doctor's girlfriend was broken up because the girl's parents felt that the programmer's career was unstable. This did not reflect that the programmer himself treated his girlfriend badly. Instead, it could be speculated that if there were no external factors to interfere, their relationship might develop smoothly. It also reflected that the programmer might be serious about relationships. In the information, Liu Wen, the programmer, would grant his girlfriend's every request when he was dating online. He would scrimp and save to subsidize his girlfriend. Although he was scammed, it could be seen that he treated his girlfriend very well in this relationship. Therefore, one couldn't simply judge whether a programmer treated his girlfriend well or not. The performance of different programmers in their relationships would be affected by a combination of factors, such as personal personality, financial status, and how busy they were at work. " When a programmer meets a psychologist " is equally exciting. Everyone is welcome to click to read it!

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!

It was not recommended to monitor other people's phones. This was an invasion of other people's privacy. However, from a technical point of view, in some cases, the following methods could be used: If it was an Android system and an Apple system, remote control software could be installed on two mobile phones (some application stores had such software). After the installation was completed, one of them initiated control and the other one accepted control. Then, the user could monitor the operation content of the other mobile phone interface. However, this method required the monitored mobile phone to agree to install the software. In addition, it was reported that there were some illegal activities, such as using a loophole in the Android system, spending about 2000 yuan (for the Android system) to obtain software from some sellers, installing files on the accused mobile phone (automatically set the permission and hide it after opening), and then installing the corresponding files on the other mobile phone to carry out comprehensive surveillance. However, this kind of behavior was illegal and immoral. "When a programmer meets a psychologist" is equally exciting. Everyone is welcome to click to read it!

Some programmers had high standards when it came to finding girlfriends. On the one hand, some programmers thought that they had studied hard, had high IQ, and had high salaries in first-class Internet companies, so they had the capital to have higher requirements in terms of appearance, income, family conditions, etc. when looking for a girlfriend. On the other hand, there were also programmers who were unrealistic. They thought that interesting souls and beautiful skin were more important, or they just wanted to find an ordinary girl with a good personality. " When a programmer meets a psychologist " is equally exciting. Everyone is welcome to click to read it!

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!

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!