[t43562]

I became a tech lead and a line manager not too long ago. It's very difficult to keep your technical edge and also deal with the the meetings, the debates about what to do next quarter, the personal issues and yet be able to zoom back down to how the hell I'm supposed to add my bit of code into this design in a sensible way that will work...what the hell is going on with this incomprehensible bug...etc.

TLDR: the use of BLAME is not that helpful. We're all human and fallible. We don't want to get to the point of blame in the first place anyhow. We want to solve problems before they go badly wrong and blame is really just about what we try to do to make things better in future. Like, if you say "this person is the one who screwed up - they're just an idiot" that lets everyone else off the hook and lets the company not change itself at all. So I don't think that mode of searching for a scape goat is very useful. What's useful is that when there are several people and none is sure who should take on some problem then you need to clarify who is most responsible and should follow up and keep chipping away at it till it's solved.

I wrote a lot of other boring crap and deleted it to spare you the pain of reading it. Yes I'm technical but it's impossible to be technical in all areas. I do write code and I'm always struggling to keep up with the other developers on the team. I have specialist skills but they're only of limited relevance to this company and this team and skills become less and less relevant. It's very hard to deal with problems in a domain that you're not familiar with but you end up being forced to deal with things that you're not equipped for because nobody else really is and you're responsible.