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!
Is it hard for programmers to find a girlfriend?
It was difficult for programmers to find a girlfriend, but it was not absolute. Judging from some phenomena, it was more common for female programmers to be young and beautiful but single. The reasons included their strong abilities, working in large factories or big cities, having higher requirements for choosing a spouse, and having a narrow social circle after work. They were not good at showing themselves. Male programmers also faced similar problems, such as having a single life after work, not being good at dressing up and expressing themselves, etc., which would also affect finding a partner. However, programmers also had some ways to find a girlfriend. For example, you can take advantage of technical exchange opportunities to meet like-minded people in technical exchanges, workshops, and open source community activities; through friend introductions, friends can often introduce suitable people according to their personality and preferences; use online social platforms, but pay attention to choosing formal and safe platforms; participate in interest groups or activities, and meet new people in interest-related activities. At the same time, in the process of finding a girlfriend, programmers could also pay attention to their personal image and self-cultivation, expand their social circle, clarify their needs for a girlfriend, show their true self, show their talent and economic strength, communicate effectively, maintain patience and perseverance, and pay attention to safety. However, there were also some disadvantages. For example, some programmers were taciturn, simple-minded, honest, easily deceived, and in a relatively weak position in emotional relationships. These factors might make it relatively difficult for them to find a girlfriend. " When a programmer meets a psychologist " is equally exciting. Everyone is welcome to click to read it!
Do programmers work hard?
The work of a programmer was hard. In terms of working hours, when the project was close to release, overtime was the norm. For example, in the three to five days before release, most programmers would encounter situations such as joint testing, emergency repairs, and emergency function launch. It was considered early to leave the company from 10 to 11 p.m., and there were even cases where they worked until the next morning. Moreover, the workload of the relevant personnel during the release of the big factory was very high. For example, the release manager and the operation and maintenance team started work at 9:00 on the release day and usually got off work at 9:00 the next morning. If there was a release problem, the relevant personnel would get off work even later. Sometimes they would work for 24 hours or even longer, and the release frequency was about once and a half months. In order to make the products comply with the regulations or check the problems, the programmers needed to work hard for a long time. For example, in order to make the products comply with the regulations, a team in a certain large factory would leave at 1 or 2 am the next day for a month. After returning home to rest, they would return to the company at 10 or 11 am the same day. Some people were even so tired that they went to the hospital. There were also groups that would have 48 hours of meetings in the conference room to check the problem, with no breaks in between. After that, the programmers would continue to work for nearly 24 hours until the repair version was released before going home. In addition, many programmers didn't have a clear boundary between work and rest. Even when they slept, they had to keep their phones by their side on standby. This was the case 365 days a year. Once they encountered an online problem, their phones would alert them and they had to solve the problem within a specified time. For example, they had to go online in 5 minutes, give the reason in 10 minutes, and report it even if they didn't solve it within 15 minutes. These situations all showed that programmers worked hard. " When a programmer meets a psychologist " is equally exciting. Everyone is welcome to click to read it!
Do programmers have a hard time reading novels?
It depends. Some programmers might have a hard time due to long hours at work leaving little time for leisure reading. But others might enjoy it as a way to unwind.
Do programmers have a hard time reading novels?
Yes, they might. Programmers are used to logical and structured thinking. Novels often have complex emotions, various plot twists, and rich descriptions which may be hard for them to adapt to.
Do programmers have a hard time reading classic novels?
Yes, sometimes. Classic novels often use archaic language and complex sentence structures. Programmers, who are more accustomed to modern, straightforward programming languages, may struggle with this. For instance, Shakespeare's works with their Elizabethan English can be quite a challenge.
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!
feelings of programmers
Will programmers be eliminated?
It was unlikely that programmers would be eliminated. In terms of job content, writing code, testing software, debugging programs, and teamwork to complete projects required professional programming knowledge and skills. This was the field of expertise of programmers. For example, when writing code, one had to use different programming languages to create efficient and maintainers according to the needs of the project. This process required a solid programming foundation and good coding habits. In terms of testing software, programmers had to write test cases to ensure that the code ran normally and fix bugs in time to improve the stability of the software through various testing methods. When they debugged the program, they had to use analysis logs and use debuggers to find the root of the problem and fix it. From the perspective of career development, from junior programmers to intermediate and senior programmers, and even to management positions such as technical managers, as experience and skills continued to accumulate, programmers 'technical and management abilities continued to improve, and their roles in projects became more and more important. However, programmers faced the challenge of rapid technological updates. New programming languages, frames, and tools were constantly emerging, which required programmers to continue learning new knowledge and skills to keep up with the pace of technological development. If they could not adapt to this change, they might face difficulties in their career development. However, this did not mean that the entire community of programmers would be eliminated. " When a programmer meets a psychologist " is equally exciting. Everyone is welcome to click to read it!
Recruiting programmers
The following is the information about the recruitment of programmers: * * 1. Recruiter's perspective ** 1. * * Recruitment requirements and salary ** - Different regions and different types of enterprises had different needs for programmers, and their salaries were also quite different. For example, in Huizhou Boluo County, the salary range of the current technical secondary school students was 5 - 8K; in Dongguan-Humen Town, the salary range of the Android development programmer was 10 - 15K for undergraduate students with one year of work experience. - When companies were hiring programmers, in addition to considering work experience and academic qualifications, they would also set salaries based on specific technical skills. For example, it involves a specific programming language (such as Java), a specific programming task (such as the production of an ATM program), and so on. 2. * * Recruitment Channel ** - Comprehensive recruitment websites such as Zhaopin.com, 51Carefree Future, Boss Direct, Lagou.com, and Hunting were common choices. There were many posts on these websites, but the workload of filtering information was heavy and the competition was fierce. The feedback might be slow. - The company's own channels: the company's official website or public account will publish recruitment information. This was suitable for job applicants with clear goals. The job information was comprehensive and updated in a timely manner. - Social media: There are a lot of job information and talent resources on platforms such as Pulse and LinkedIn. In addition, industry communities such as Zhihu, CSPD, developer headlines, Sifou, and Open Source China could also provide job opportunities. They could attract the attention of employers by perfecting information, posting job information, and participating in community discussions. - Headhunter recommendations: Internet headhunters can quickly match positions, but the headhunting market is mixed. You need to identify their professionalism and areas of expertise. - Personal community: Including WeChat group and QQ group, there are two types of technical guidance group and recruitment group, which will release targeted recruitment information. - Personal branding: Attract potential employers by posting Bilibili videos, TikTok videos to show professional abilities and project experience, or writing technical blog posts to show off work results. - Internal recommendations: Internet companies such as Byte, Xiaomi, Ali, and Baidu have internal promotion channels. Internal promotion positions are sometimes not seen in the market and the demand is very urgent. The success rate of interview may be higher. - Human Resources: Use social networks, Alumni Associations, Fellow Villagers, and other means to get to know more people and obtain job opportunities. 3. * * Biases and considerations in recruitment ** - Some companies had prejudice against older programmers, such as thinking that older programmers were not as motivated as young people, unwilling to work overtime, or worried that they could not keep up with technological changes. However, in reality, there were many older programmers who were experienced, technical, and responsible. Some companies would think that older programmers were expensive and cost-effective, but there were also older programmers who were willing to lower their salary requirements to fight for opportunities. * * 2. Job Seeker's Perspective ** 1. * * Job Seeker's own conditions and salary expectations ** - A job seeker's education, work experience, technical skills, and other factors would affect their salary expectations and job competitiveness. For example, the salary of a 3 - 5 years working experience in Beijing may be 3,000 - 5,000 yuan per month; in Xi'an, an undergraduate programmer with 1 - 3 years of working experience can be paid 8000 - 10000 yuan per month. 2. * * Choice of job search channels ** - Choose different job search channels according to your own situation. If it was a fresh graduate or a job seeker with less experience who wanted to cast a wide net, a comprehensive recruitment website might be an option, but they also had to pay attention to other channels. If you are interested in a specific company, you can pay attention to the company's own channels. Those who wanted to make use of their connections could seek opportunities through internal recommendations and connections, while those who wanted to show off their technical strength could attract employers by establishing a personal brand. "When a programmer meets a psychologist" is equally exciting. Everyone is welcome to click to read it!