10 industry insiders should know

If you plan to engage in the IT industry or just enter this industry, the small inside story below may scare you, because these things will not be publicly discussed. If you are an IT veteran, you may have met most of them. If you want to, please join in the discussion.

These are mostly for network administrators, IT managers, and desktop support professionals. Although these tips are not targeted at developers and programmers (these two types of people also have their own tips .), But some may also apply to them.

　　10. Although the IT industry pays better than many other industries, some companies regard you as a "servant ".

Although it salaries are not as good as they were before the Internet bubble, it salaries are even better than those in other industries. In the next few decades, the amount of technology in business and social development will continue to increase, so we have reason to believe that the demand for IT professionals will not decrease.

However, because it salaries are generally high, some companies think that you are the "servant" of the company and have your right to allocate money, whether at work or not.

• Example 1: When someone works overtime (encounters a problem) and you receive a technical call from him/her at, you may hear "this is part of your work ."
• Example 2: To avoid downtime during work, it takes six hours to configure/upgrade software on Saturday. You are willing to hear "we have paid you a lot ".

　　9. Some users are clearly wrong about themselves, but they will still blame you.

When some users encounter problems that cannot be solved by themselves, they will show you their profound "Lion's Roar ". They will roar, "What's wrong with this? Unable to access the network !" Or "this computer cannot be used at all !" Or, "What have you done on this computer ?" In fact, the root cause of the problem is that they accidentally deleted the IE shortcut on the desktop, or they accidentally removed the mouse plug, or accidentally spilled boiling water/coffee on the keyboard.

　　8. It may be normal to wander between "Scapegoat" and "Hero" every day.

If you had a network problem with many colleagues 10 minutes ago, you would have done it. But they don't really want to solve this problem. They actually think of you as a hero at that moment. But a few hours later, when they were printing, they were in trouble due to slow network speeds. Your troubles also came, and the halo of your hero disappeared. You became the number one scapegoat for that moment. But before that day, you shared a simple and convenient outlook technique with other colleagues, and the hero's halo fell on your head again.

　　7. Although the certificate is a stepping stone for a job, it cannot prove that you must be a good technician.

Both headhunting and HR departments like it certificates. They use certificates to determine if job seekers match their positions, and they also use certificates to filter job seekers. You may hear many IT veterans say that "XX has obtained an offer certificate", and "XX" does not have the experience required for that position. There are many examples. But it is undeniable that the certificate is indeed a "stepping stone" of the post ". They indicate that you are an advanced young man and that you want to expand your skills and improve your abilities. If you are an experienced it person and have a certificate that matches the experience, you will find yourself very popular. If you have a technical certificate, you can describe your basic knowledge and become a professional. However, most certificates do not indicate how competent you are.

　　6. Your non-technical colleagues will regard you as the technical support of their families.

When your non-technical colleagues (or friends, relatives, and neighbors) encounter computer or network problems, they will send an email, call or come to your office and ask you how to kill the virus, ask you how to solve the problem of wireless routing and how to upload images and videos to the Internet.

Some of them may even say, "XX, I want to bring my computer here (in the office). You can do it ." Although some people will politely pay you, some hope and hope you can help for free. Although there is nothing wrong with helping them, you need to know the bottom line and when to refuse. If you are not good at rejection, refer to "10 methods of improper free technical support ".

　　5. When everything goes well, the consultant will do his best. When something is wrong, it is your fault.

Working with IT consultants is an important part of the work and a very challenging task. Consultants use their niche expertise to help you deploy/configure professional systems. when everything goes well, you are friendly and cooperative. But you must be cautious. When things are not doing well, some consultants will blame you for the mistakes, and say that their solutions have been well done elsewhere, which is impossible, the problem must be with you. On the contrary, when the project is very successful, some consultants will try their best to ignore the large amount of work you have done (for example, tailored improvements to suit the company's own development ).

　　4. It takes much longer to maintain the "old" technology than to implement the "new" technology.

In the IT industry, there is a concept that is very attractive-playing with the latest cutting-edge technology. However, this concept does not apply to most IT jobs. Generally, IT personnel spend more time maintaining existing technologies than implementing new technologies. Even those IT consultants who have the ability to use most of the latest technologies are more willing to adopt existing and effective solutions than those composed of cutting-edge technologies.

　　3. Senior IT personnel are usually the biggest obstacle to achieving new technologies.

Many companies are capable of adopting cutting-edge technologies. Taking the time to update/replace software/architecture can potentially save costs or increase productivity and profitability. However, in many cases, the barriers to porting to new technologies are not insufficient budget or management problems, but senior technical staff in the IT department. Many it veterans are resistant to new technologies and do not want to change. Of course, you cannot say that this is a bad thing, because to maintain the stability of the existing structure, you still need existing technologies. But they cannot use this as an excuse not to learn new technologies or expand new directions. Some people even become lazy and complacent.

　　2. When selecting technology, some IT personnel should consider the impact on themselves rather than the business.

In addition, some IT people have a secret and need to speak out. Their selection criteria are: to see if these technologies depend heavily on their business, rather than whether these technologies are truly suitable for the business itself. For example, some IT people prefer to choose solutions that require professional skills to maintain, rather than those that can be used. In addition, even if the windows solution is better, some IT managers usually choose a Linux-based solution instead of a Windows solution because they have many Linux/Unix backgrounds. (Of course, if you have a Windows Background, you will skip the Linux solution .) There are many excuses and reasons for similar examples, but most of them are hypocritical.

　　1. IT people often use terminology or line-by-line to spoof technical managers, so as to cover up the mess.

Not all events done by IT people are successful, and even the best ones will make mistakes. However, not all IT personnel are good at recognizing mistakes after making mistakes. Some people, after messing up things, make full use of the technology that business managers are not very familiar with (even some high-level technical managers cannot cover everything), and then use terminology or slang to spoof them. For example, after explaining to the business manager why the financial application has been suspended for three hours, the technical staff may say, "when the program is running, the SQL Server blue screen is displayed. Damn Microsoft !" He did not mention the real reason for the blue screen-the driver was not tested on the server after the update.

-------------------------------------------------------------------