9 reasons that prevent you from becoming a timlid
Hah It seems that the tmilid does nothing but drags pieces of paper, drinks a lot of coffee, jokes some jokes, and indeed he is some kind of strange guy. Why don't you take his place? You have a lot of experience, you know the command like the back of your hand, you master C ++, C # masterfully, Java and what can I say - you are a programmer from God!
Only now the management does not notice that "you are here for the whole team, dragging around" and pull out projects a week before the deadline. In short, it's time for you to lead! You sleep and see how cool everything goes with you, productivity increases, tenders one by one, the universal recognition of the team and the authorities are yours. That's just the increase left to get. And now to the point. What all the same prevents such a steep specialist as you take everything out of the swamp and rule the world?
')
For example:
You have to be a leader, because any leader leads a team, causes trust, friendliness, and in general he is a cool guy. But now is not about that. We are not talking about the usual leader or head of the advertising department. We're talking about the leader of a team of strong developers who still troll Lena from the HR department for what she called HTML programming language (ha ha ha). Hmm, so here. Look at the 9 reasons that prevent you from becoming a team leader:
1. You can not quickly make decisions
And this is not your fault. Well, not quite. You just do not have enough experience to quickly make the right, optimal, balanced decision. According to the Stack Overflow study , 48.3% of developers recognize their work as a hobby. And if you choose the software architecture, programming language and offer an alternative to the customer is much harder than to decide which car to steal in the GTA - think about it, do you need it? Because the work that does not bring pleasure = doom yourself to the endless cycle of hell. Ta-dam!
2. You can’t say no
Yes, you are just a kind guy who is always happy to help (even if this is not at all a joy to you). You scored a lot of work, and even finish everything for everyone. No, you will definitely become not a leader, but a person who allows you to sit on your neck, but also help you to climb. You should be able to say no. Timlid, who spends the night at work and completes everything for everyone - a strange leader. Let's add a little logic and understand that if a team does not deliver the modules on time, then the manager is far from a pro. Well, can not the whole team be Krivoruk?
3. The organizer of you is not very
Perhaps you have a huge amount of ideas and an endless stream of creativity. It is understandable (sometimes you have to invent such crutches)! Only here on the embodiment of ideas into reality, it takes you, in the literal sense, an infinite amount of time. You offer and do nothing. “You need to implement Agile” - you said, and for six months now you continue to work on a cascade model. “Let's run down the internal stack with source codes!” - well, you understand ... Put ideas into life and you will be noticed. Initiative workers are generally appreciated, and developers are even more so.
4. You are passive
Going to a bar in the evening - “nooo”, go on a business trip - “nooo”, blog and share life hacks - “zacheeeem?”, Gash with a useful piece with colleagues - “I have nothing to do?”. All this matters too. 1, 88 are points in which HR evaluates your input to open source applications. Doing something for the soul or “for fun”, you show that you really enjoy working. Such employees are valued because they are ready to bring more benefits to the company than employees who work hours.
5. You often make mistakes
Maybe not in the code. You have forgotten that today there was a planning meeting and were late. You forgot to move the sticker on the scrum-board, forgot about the deadline, forgot, forgot, forgot ... These are also errors that influence the opinions of others about you.
6. You think that communication skills and communication skills are only needed by the sales manager.
Sociability is the main skill noted by HR specialists in the Stack Overflow study. Imagine your team taking on a huge project. You broke the product into 10 modules, and each developer took himself to work on the module and wrote the code without interacting with the others. Now everyone writes in different languages, there are no single variables, all works in different stages seem like a bad dream. Sociability is needed for productive and high-quality team work. If the whole development department consists of couch potatoes and introverts - nothing good will come of it. Timlid communication is needed to interact with the team, management and customers. Clarification of requirements, conflict resolution (yes, you will postpone the dates and begin), communication with users and drafting user scripts. Now you will talk more than code: (
7. You think you can do everything yourself.
Need to be able to share. And even work. If you do not delegate working powers - die or just burn in the workplace! Such a team leader is not needed neither by the team, nor by the management. You do not have to be dead in the middle of a project. To think about yourself, in part, to think about your team, which hopes for your help and participation. Therefore, share the work and distribute small tasks to other participants. Tasks for the trainee type "Bring coffee" - not at all. Ask a colleague to gather the rest of the participants for the planning meeting or ask each of them to write the desired tasks (and it’s convenient for you to draw up a schedule and do well for them).
8. Learn the basics of management for your humiliation.
In university years, together with classmates, you laughed at the guys from the Faculty of Economics - “Hmm, the poor will face the fate of a free cash register.” And now you had to learn the basics of management, calculations in Excel, project planning and other “enterprise shame”! Do not torture yourself. If this item is about you - hammer and forget - you will become an excellent tech-lead. Because the team-lead always bears the burden of paperwork, communication with the customer and, no matter how regrettable it may sound, management.
9. You just don't tell anyone.
You talk about your desire to colleagues or leadership. The 21st century is the century of technology, but for some reason, telepathy is not in trend. This is primarily for you. If you really want to try on the role of team leader - forward to leadership. Tell us about your desire: what you want to bring, what to change, remove, and why you should lead the team. And you can take and send a response to the job lead team in a cool company.
Only now the management does not notice that "you are here for the whole team, dragging around" and pull out projects a week before the deadline. In short, it's time for you to lead! You sleep and see how cool everything goes with you, productivity increases, tenders one by one, the universal recognition of the team and the authorities are yours. That's just the increase left to get. And now to the point. What all the same prevents such a steep specialist as you take everything out of the swamp and rule the world?
')
For example:
- Do you think flexible methodologies for wimps
- Think Timlide is only in charge
- Think that the team leader only checks for all the code
- Think it's just a cool dude.
- You think too much
You have to be a leader, because any leader leads a team, causes trust, friendliness, and in general he is a cool guy. But now is not about that. We are not talking about the usual leader or head of the advertising department. We're talking about the leader of a team of strong developers who still troll Lena from the HR department for what she called HTML programming language (ha ha ha). Hmm, so here. Look at the 9 reasons that prevent you from becoming a team leader:
1. You can not quickly make decisions
And this is not your fault. Well, not quite. You just do not have enough experience to quickly make the right, optimal, balanced decision. According to the Stack Overflow study , 48.3% of developers recognize their work as a hobby. And if you choose the software architecture, programming language and offer an alternative to the customer is much harder than to decide which car to steal in the GTA - think about it, do you need it? Because the work that does not bring pleasure = doom yourself to the endless cycle of hell. Ta-dam!
2. You can’t say no
Yes, you are just a kind guy who is always happy to help (even if this is not at all a joy to you). You scored a lot of work, and even finish everything for everyone. No, you will definitely become not a leader, but a person who allows you to sit on your neck, but also help you to climb. You should be able to say no. Timlid, who spends the night at work and completes everything for everyone - a strange leader. Let's add a little logic and understand that if a team does not deliver the modules on time, then the manager is far from a pro. Well, can not the whole team be Krivoruk?
3. The organizer of you is not very
Perhaps you have a huge amount of ideas and an endless stream of creativity. It is understandable (sometimes you have to invent such crutches)! Only here on the embodiment of ideas into reality, it takes you, in the literal sense, an infinite amount of time. You offer and do nothing. “You need to implement Agile” - you said, and for six months now you continue to work on a cascade model. “Let's run down the internal stack with source codes!” - well, you understand ... Put ideas into life and you will be noticed. Initiative workers are generally appreciated, and developers are even more so.
4. You are passive
Going to a bar in the evening - “nooo”, go on a business trip - “nooo”, blog and share life hacks - “zacheeeem?”, Gash with a useful piece with colleagues - “I have nothing to do?”. All this matters too. 1, 88 are points in which HR evaluates your input to open source applications. Doing something for the soul or “for fun”, you show that you really enjoy working. Such employees are valued because they are ready to bring more benefits to the company than employees who work hours.
5. You often make mistakes
Maybe not in the code. You have forgotten that today there was a planning meeting and were late. You forgot to move the sticker on the scrum-board, forgot about the deadline, forgot, forgot, forgot ... These are also errors that influence the opinions of others about you.
6. You think that communication skills and communication skills are only needed by the sales manager.
Sociability is the main skill noted by HR specialists in the Stack Overflow study. Imagine your team taking on a huge project. You broke the product into 10 modules, and each developer took himself to work on the module and wrote the code without interacting with the others. Now everyone writes in different languages, there are no single variables, all works in different stages seem like a bad dream. Sociability is needed for productive and high-quality team work. If the whole development department consists of couch potatoes and introverts - nothing good will come of it. Timlid communication is needed to interact with the team, management and customers. Clarification of requirements, conflict resolution (yes, you will postpone the dates and begin), communication with users and drafting user scripts. Now you will talk more than code: (
7. You think you can do everything yourself.
Need to be able to share. And even work. If you do not delegate working powers - die or just burn in the workplace! Such a team leader is not needed neither by the team, nor by the management. You do not have to be dead in the middle of a project. To think about yourself, in part, to think about your team, which hopes for your help and participation. Therefore, share the work and distribute small tasks to other participants. Tasks for the trainee type "Bring coffee" - not at all. Ask a colleague to gather the rest of the participants for the planning meeting or ask each of them to write the desired tasks (and it’s convenient for you to draw up a schedule and do well for them).
8. Learn the basics of management for your humiliation.
In university years, together with classmates, you laughed at the guys from the Faculty of Economics - “Hmm, the poor will face the fate of a free cash register.” And now you had to learn the basics of management, calculations in Excel, project planning and other “enterprise shame”! Do not torture yourself. If this item is about you - hammer and forget - you will become an excellent tech-lead. Because the team-lead always bears the burden of paperwork, communication with the customer and, no matter how regrettable it may sound, management.
9. You just don't tell anyone.
You talk about your desire to colleagues or leadership. The 21st century is the century of technology, but for some reason, telepathy is not in trend. This is primarily for you. If you really want to try on the role of team leader - forward to leadership. Tell us about your desire: what you want to bring, what to change, remove, and why you should lead the team. And you can take and send a response to the job lead team in a cool company.
Source: https://habr.com/ru/post/329882/
All Articles