TL; DR:
Context Switching -- The Tax Nobody Budgets For
I went into the ExperiencedDevs subreddit and found a discussion about task switching that I wanted to dig into. This is probably one of those topics where if you've been a software engineer for any length of time, you've felt the pain of being pulled in multiple directions. And if you're an engineering manager, you've been on both sides of it -- getting randomized yourself AND being the person asking your team to switch gears.
I wanted to talk about this from a few different angles: as someone who was a software engineer constantly dealing with context switching, as an engineering manager who has had priorities shifted on my teams, and as the person who sometimes has to be the one delivering the new priority to my team. As usual, I'll throw this disclaimer in -- anything I say comes from my own lived experience. It's not the only way to look at it. Just my perspective to hopefully give you some different insights.
You can check out my full thoughts on this in the video below:
This content is only available for members.
Become a Member
Or subscribe to the free Dev Leader Weekly newsletter for C#, .NET, and software engineering content every Saturday.
