Shulou(Shulou.com)06/01 Report--

IT workplace newcomers encounter what common misunderstandings, many novices are not very clear about this, in order to help you solve this problem, the following editor will explain for you in detail, people with this need can come to learn, I hope you can gain something.

There must be amazing newcomers, who often develop some very good ways of doing things and working habits in school or after entering the workplace, with high efficiency, high output, and even bringing new people in a very short period of time. Rookie of the year deserves it.

However, it seems that more employees do not perform well. These employees have short working hours (such as fresh graduates or less than two years of graduation), especially introverted ones tend to fall into the quagmire of mistakes and are unable to extricate themselves. and these wrong behaviors will have a very negative impact on future development, leading to further and further failure in the workplace.

I would like to elaborate on it from the following angles:

1. Unwilling to communicate with colleagues, unwilling to learn more from colleagues

Most of this kind of employees are introverted or a little cold in temperament, but they do not realize that if there are three people, there must be a teacher. Learn more from colleagues and exchange needed goods, which will do no harm to your future development. With mentoring or veteran staff, the situation may improve, but if the internal factors do not change, the final effect is still not optimistic.

It is normal to encounter some technical problems in technology development, of course, independent thinking is valuable, but corporate projects often have a certain time limit, giving priority to solving problems is always the first place, instead of a person struggling and searching for solutions. If the pressure of time is not great, it is OK to think more about it. Considering the delivery pressure, you need to actively communicate with colleagues and technical managers to find solutions. Usually, active communication is better than going it alone. Maybe a sentence from a colleague or boss answers that ancient poem. It looks like there is no road, but there is another village around the corner. At the same time, I also established a better friendship with my colleagues and left a good impression on the boss that I had a way of doing things.

two。 Narrow vision, only focus on their own acre of land, limited to the role

This kind of situation is very common in the workplace, and it is even more harmful. Not only junior programmers, but even programmers who have worked for more than five years have similar problems, not ignoring their own affairs. Company projects are often large and comprehensive, if you only focus on their own corner, then there will always be only trees, not forests.

I'm sure no boss will mind that the following programmers take on more responsibility, do more things, and finally make the project team more productive. Since the boss does not mind, then you should boldly jump out of your scope of responsibility, look at other projects of the company, and enrich your industry knowledge.

Do not avoid things outside your duties and try to bear more if you can help. To help others is to improve yourself, and that's what teaching and learning means. Moreover, you have helped others this time, and the next time your project is tight or encounter technical problems, the recipients will definitely return the favor, thus creating a benign atmosphere of mutual assistance, and the output of the whole project team will increase at the same time.

Generally speaking, the best strategy for a company to promote a person is to let the candidate do what the position needs to do in the future. If you do a good job, you should be promoted. If you don't do well, you can find the employee's problems in advance, postpone the promotion, and need to investigate for a longer period of time. The cost of such trial and error is undoubtedly the lowest.

3. The pattern is too small, turning a blind eye to technologies outside the project, outdated knowledge, lack of skills, and extremely simple skills.

In fact, the problem of the whole IT industry is talked about here, and the technology is developing too fast. It is mainly a topic of continuous improvement of competitiveness.

Today is still desktop development, tomorrow web development will become mainstream. Finally mastered the relational database, No-SQL has become the mainstream. After a lot of effort and proficiency in static languages such as Java and C #, it is found that dynamic languages GO and Python have become standard for cloud computing and machine learning. Mobile development was Object-C and Java yesterday, but today it becomes Swift and Kotlin.

Of course, this is not to say that we should keep up with the trend and hold on to fashion. In doing so, there is no other result except to be tired and tired to death on the workbench.

In fact, as long as you choose a direction, in-depth learning and accumulation, there will be success. For example, if you are familiar with Java, you are absolutely familiar with learning Kotlin. If you have a solid foundation in relational databases, it must be easy to master MangoDB.

Programming ideas and problem-solving ideas are the same, usually study and work should be good at thinking, inference. And keep pace with the times, update their knowledge base and skill attributes in time, and maintain good market competitiveness. Think more after doing something, how to do it better, and look at things from a higher point of view.

Let me give you two practical examples:

Programmer An in a state-owned enterprise, continue to develop Windows Form, procrastinate mainly, add, delete, modify and query the SQL Server database for as long as five years, suddenly plan to leave one day, look at new opportunities, thinking that with five years of work experience, you can easily find a better job. But in fact, the road to job search is extremely difficult, nominally five years of work experience is actually an extremely single skill that has been reused for five years. And the environment has also changed, the mainstream has been web development, mobile development. Because you don't update your knowledge base and skills reserve in time, you may not be able to jump when you really want to change jobs.

Programmer B in a foreign company, the atmosphere is relatively comfortable and relaxed, the pace of the project is slow, seems to have done a lot of projects, but the project is almost similar, the difficulty is general, involving a wide range of areas, but the technical points are all scratching the surface. After three years like this, in fact, the accumulation is relatively loose, the depth of knowledge is not deep, and the core skills have not been developed.

4. Have no idea about the future, don't think about what you want to do in three or five years.

I myself made a similar mistake, and by the time I woke up, three years had passed.

The first three years of a programmer's career are actually a very important period of polishing and planning. If you spend it in confusion, you will surely sigh when you think about it afterwards, but there is no reason to return.

Having a goal without a specific plan is just a vision. It is suggested that both junior and senior programmers should actively communicate with their predecessors or direct bosses to see if they have any plans and suggestions worth learning from.

The taboo in the workplace is to passively wait for the arrangement of fate. I was also waiting for my boss to help me plan the future at the beginning of my career. Up to now, ten years have passed, and I have not waited until …... So the boss will not take the initiative to help you plan for the future, the most important thing is your own requirements and expectations.

5. I don't realize whether I work for myself or for the company.

This is also a very good topic, many people have not figured it out, even some programmers who have been working for ten years. If you want to understand this, it will be much better to be motivated to work. Self-driven to make work more interesting and meaningful.

The big boss of a well-known Internet company in China once said that it is worth pondering. "I pay you 200000 a year, that is, 1 million in five years. If you dawdle around here, you must be the last to lose. Is your five-year youth only worth 1 million?"

Therefore, the sense of ownership of newcomers in the workplace must be strengthened, and you should continue to improve your ability and strengthen your ability to create value.

For example, if the company is paying you 200000 a year, then you should have a goal of bringing far more than 200000 of the revenue to the company.

If you have this ability, the company will certainly repay you accordingly. If the company doesn't give you a promotion and a raise, just walk away and have a good time. High-quality talents are always scrambling for it.

6. Don't want to go out of the comfort zone and dare not try new things.

This point varies from person to person and cannot be forced. This topic is actually a bit broad. If you are doing very well in one direction and the returns are good, there is nothing wrong with not wanting to set foot in other areas.

The only constant in the world is that the world is changing all the time. The jobs left today may disappear tomorrow. If the world wants to abandon you, it won't say hello.

For example, if you are an expert in SQL Server or Oracle at the company, but the company plans to switch to non-relational databases, if you are afraid of change or even refuse to change, it means you may miss out on another brand new data storage platform and miss out on a lot of opportunities, and those who are willing to accept change and adapt to the trend will certainly get better returns of the times.

For example, if the technology you are using is just enough for everyday projects, should you try something new and refresh your technology stack from the perspective of improving the user experience and using more mainstream technology? why not kill two birds with one stone?

Another example is that a senior programmer is used to the long-term slow-paced work atmosphere, because the company restructuring was laid off, but he soon joined a domestic first-tier Internet company, but could not adapt to the fast pace of the Internet at all. he left his job for a period of time under the pretext of "chaos" in company management and "frequent" changes in strategic planning. After a long time can not find a suitable job, coupled with middle age has arrived, if you do not actively adjust, the rest of your work and life will be fraught with difficulties.

Is it helpful for you to read the above content? If you want to know more about the relevant knowledge or read more related articles, please follow the industry information channel, thank you for your support.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.