Answer the question
In order to leave comments, you need to log in
The problem of relations between "newcomers" and "oldies"
Imagine the situation: You are a hardened programmer, you have 20 years of experience. But one day a newcomer comes to your team, who is well prepared and damn smart and quick-witted. And sometimes he starts giving you advice. Of course, this is also a question of education, but still: how do you react to this?
PS Personally, I would still be interested, since it is in dealing with competent specialists that you can learn a lot of new things for yourself.
Answer the question
In order to leave comments, you need to log in
It all depends on advice. Often beginners think that they are smarter than everyone around and see the truth. In fact, their truth is a rake that you have already stepped on an unlimited number of times.
If the advice is practical, a specialist with any experience should listen. But, unfortunately, this most likely will not happen. Experienced specialists, as a rule, also have a strong aplomb, which can be removed only by working on oneself. But few people take the time to do so. If I am responsible for myself, then I would like to believe that I will listen to newcomers.
Often just beginners are useful with new academic knowledge, it is necessary to learn this fresh knowledge from them. You give him experience, he gives you new knowledge.
And what about age?
If a person is right, then he is right, regardless of age. If he is wrong, then he is wrong, regardless of age. Everything else is stereotypes that only interfere with life.
A lot depends on the form of advice from a beginner, for example, such situations:
1. I see you do like this and I was taught like this and like that, please explain what the rake is? - An excellent option, the beginner shows his knowledge and allows the old man to "save face" everyone is happy.
2. Well, you and ... With such experience, you write such a mess, haven't you been taught or what? “Disgusting option, no matter right or wrong advice, but the newcomer will be sent… somewhere.
Accordingly, the conclusion is that the authorities should have a conversation with newcomers about subordination in the team and clarify who is who. Then the newcomer will be helped and he, in turn, can bring fresh ideas, and the atmosphere in the team will be normal.
Usually in the beginning, anyway, people look at each other. After a couple of months, well, a maximum of half a year, it becomes quite clear what a person is like and, accordingly, how to relate to him and his advice. Usually, age differences during this time are also somehow leveled out or something. And at first, it’s better to just do your job, if you do it well - adequate colleagues themselves will not hesitate to ask for your advice.
However, there are also beginners who do not understand where they are climbing, and old people who poke their age with or without reason. That those that others are personally unpleasant for me, but here it’s hardly possible to change something :(
As noted above, “well-prepared and damn smart and quick-witted” is not the same as “knows how to do it right”, if only because it cannot yet know “how it should be”, because theory and practice are different things. A simple example is to solder the wire beautifully and correctly. As a beginner can know correctly, but you can do it beautifully only with experience.
On the other hand, "you have 20 years of experience" means very little in today's world. Constantly have to learn.
20 years of experience means nothing. Maybe this person has been riveting primitive forms in 1C for 20 years, delphi and visual basic, and the young man knows linux, C ++, Ruby and Haskell.
If Steve Jobs and Bill Gates had listened to the “old men” at IBM, instead of iPhones, we would now be buying bulky ugly mainframes with typewriter terminals.
It usually happens like in the army. A rookie goes to wash the floors and peel potatoes)
softh12, how can I contact you? mail, skype, contact?
maxyc.webber 8128305 [email protected]
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question