<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Teamlead on DevopsTrain</title>
    <link>https://devopstrain.lifeisfile.com/tags/teamlead/</link>
    <description>Recent content in Teamlead on DevopsTrain</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <copyright>©, Alex Babochkin</copyright>
    <lastBuildDate>Wed, 06 Nov 2024 00:00:00 +0000</lastBuildDate><atom:link href="https://devopstrain.lifeisfile.com/tags/teamlead/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Is It Worth Becoming a Team Lead?</title>
      <link>https://devopstrain.lifeisfile.com/post/teamlead/</link>
      <pubDate>Wed, 06 Nov 2024 00:00:00 +0000</pubDate>
      
      <guid>https://devopstrain.lifeisfile.com/post/teamlead/</guid>
      <description>
        
          
            Let&#39;s think it through: is it worth becoming a team lead?
👾 It&#39;s not uncommon for a specialist to switch from a team lead role back to being an individual-contributor engineer. And there are reasons for that. But let&#39;s start with the upsides.
➕Pros of being a team lead:
A leadership role means less hands-on work and more organizational work. Some people prefer that and enjoy it more A bump in pay, even if a modest one Sometimes you get the chance to build a team according to your own preferences, but again, not always — sometimes you join a team that already exists You have more leverage and can build the infrastructure the way you prefer ➖Cons of being a team lead:
          
          
        
      </description>
    </item>
    
  </channel>
</rss>
