BROADCASTS.com

b'

This is a rerun of episode 220.

In this episode, Dave and Jamison answer these questions:

Questions

\\n
1. \\n

   Hello,

   \\n\\n

   I know you said you don\\u2019t read the compliments on air most of the time but this podcast is great. I just found it a few weeks ago and I love the positive fun approach to question answering. It has really made me think about software engineering outside of the \\u201c\\u201cmake code do thing\\u201d\\u201d box.

   \\n\\n

   Anyway, the question: I have been at the same company for 4 years. It is my first job out of college. I have ended up working in so many different languages and frameworks I don\\u2019t remember them all. I guess that\\u2019s just how things go. Recently I have been selected to take on a scrum master role and I feel I am quickly being groomed for management.

   \\n\\n

   That was never really my goal. I wanted to build a depth of knowledge and always have my hands on code.

   \\n\\n

   Will taking on these kind of roles hurt my chances at future technical roles? Am I dooming myself to managing spreadsheets and Jira tickets until I retire? Will I only communicate in Dilbert references?

   \\n
\\n
2. \\n

   My teammate frequently gives status updates or fields follow up questions about work that was mostly done by someone else. I am pretty sure they do this to be helpful not to claim credit for all the work. I just wish I could speak up about the work I contributed primarily to before they do so on my behalf. I wish it didn\\u2019t bother me since we are one team and I would rather focus on the progress of the team rather than receiving credit.

   \\n\\n

   How should I respond to these situations in a way that allows me to not get bothered emotionally and also do what\\u2019s best for the team?

   \\n
\\n