10+ harmful advice to the developer from managers and seniors
Recently, we at Kaspersky Lab held an online meetup where technical managers and developers from the Mobile Dev team gave bad advice about work and career. In particular, colleagues explained what to do to set fire to a release and slow down your development, and what working signals to ignore in order to constantly live in chaos.
This post briefly squeezes the ether into a few key points. If you are interested in listening to a more detailed discussion and arguments of the participants, view the recording of the meeting here or in the widget below.
Harmful advice. Work from here until lunch.
But seriously. In recent decades, the world around us has become more anxious and unstable, and even a little bit has long ceased to be a lamp-garage hobby.
In short, there is more stress, and in such circumstances, single heroes will not be able to be heroic for a long time. And so, one has to think about the so-called well-being. Any of the numerous matrix-principle techniques that are close to you personally will be suitable here, and some methods and experience of their use are given in the report. 🙂
Harmful advice. Stagnation is the norm!
But seriously. You’re lucky if your company’s culture has managers in charge of developing their colleagues and helping them grow. And if there is an internal expert from whom you can get specific advice in the context of your company, then this is a career jackpot. And it is possible to combine two experts in general: to go to the internal one, and to involve the external one, to analyze their advice and draw conclusions.
However, if the manager does not help and you have to go through this thorny path on your own (and even there are no internal experts), there is still a solution. Just ask colleagues higher up in your team what they did and how they grew. The method is pragmatic and quite effective.
Harmful advice. Do not communicate with any of your colleagues – you will be mistaken for a smart person.
But seriously. We engage in teamwork not because of someone else’s whim, but because a team can digest huge tasks much more efficiently than individual individuals.
It is obvious that the lack of communication between developers in the team can lead to fatal mistakes by the developers themselves. Well, if you don’t communicate with the manager, he simply won’t be able to distribute the task correctly — but he could give it to the one to whom it will give the biggest boost (for example, you).
Harmful advice. Neurons are evil, they will soon take away everyone’s jobs.
But seriously. Yes, neurons are already really good at writing code, but now developers are required to have high-level planning and the ability to design architecture (as well as, of course, debug bugs behind the neuron itself :)). That is, it is not just a matter of creating a feature, but first of all digging up the initial problem for the solution of which it is needed.
Harmful advice. Never return anywhere.
But seriously. “Expanding your horizons” is not just words in IT, everything is too dynamic.
You can choose different stacks and do things you’ve never done from scratch. And you can choose projects or even industries where your programming language is used, and thus immerse yourself in something new with a high threshold of knowledge.
In any case, you will win: or you can find a new stack that you like better and switch to it; or you will realize that your programming language is the best, and your love for it will grow exponentially. Or stop in the middle and master both — and then add a new school to your resume and become an even more sought-after specialist. 🙂
More detailed answers, more theses and active discussions are waiting for you in the recording of the report.
Don’t miss ours
future events
Follow, register, and we will remind you about the meeting and send you a link.