I have been with the company for over eight years. It sounds scary for an IT specialist that I have been working in one place for a long time, but it is true. It is interesting to work for this company because I have grown to be a team leader, and projects are becoming more complex and challenging.

At the beginning of my journey as a lead, I read that there are three ways to manage:
The first way is to control and force.
The second is not to control and not to force
The third is to create an atmosphere for each private team member to solve the assigned tasks independently. I am a supporter of this path.

Requirements for newcomers - six months after employment, they should merge into the overall pace of the team and project requirements. In six months, I expect independent decisions from them. Sometimes I can point out shortcomings, not correcting mistakes, but pointing out the consequences of such decisions.
The main thing is that a person wants to develop and look for his sources of information and existing and new-created approaches to implementation.

Personal Way of Leading

With the transition to remoteness, the conduct of daily calls has changed. It took more time for communication and discussion of details. We have no strict control for activities in working hours. If the developer misses our call he will notify me in advance and gives a short report. I can tell our customers about the movement and development progress at our daily stand up.

Our working relationship is based on trust. If you have to leave during working hours, you can work at another time - later in the day or on weekends. For me, honesty and transparency in communication are fundamental such as the result of work and completing tasks on time.

Influence of remoteness

Listen to people more, do not try to decide everything on your own, and do not rely solely on your experience.

In development, look for ready-made solutions from other teams and spend a little more time analyzing and adapting them to your needs. It is much more efficient than writing everything from scratch. Because sooner or later we come to the same thing that already exists. But we spend much more time and effort experimenting and abandoning non-working strategies.

From the point of view of the lead position, I would advise you to listen to the team more often and be interested in working relationships. There was an experience when smart guys left the company due to behavior and quality. A timely conversation and a cardinal decision in the direction of one employee could improve the quality of the work in the whole team.

ADVICE TO MYSELF AT THE BEGINNING OF CAREER

We have our own story in the company. When a new employee comes to us and passes the probationary period with dignity, the moment of “baptism of fire” comes. I say:

- Guys, now is the time to tell you about one developer and his "bisexual button". During mobile development, it was a task to make a button that would mirror the screen. It was necessary for localization of the application in the American and European regions. And so, one developer created this button and thought for a long time about its name. We laughed when the first of us accidentally saw his “bisexual button” and understood what the question was.

By the way, he no longer works with us, but we deliberately do not rename this button - as an example and lesson on how not to do.

So, develop yourself promptly - your experience will not include buttons with a similar name.

Our favorite joke