The initial assumption is wrong: Full-Stack engineers are not expected to traverse the whole stack with senior level skills and ease. Also if you become really

The initial assumption is wrong: Full-Stack engineers are not expected to traverse the whole stack with senior level skills and ease. Also if you become really good at something you'll realize that actually it is not all about more skills. There's a point where strategic decision making overcomes coding skills. E.g. 1: I spent years to really learn vim and git indepth. I can write my own git clone and did that before as well. However I have seen so many different editors and IDEs that I'm at a point where I can take whatever is there. I use nano with ease if the situation requries it. This makes me quicker than installing my favorite editor, my configs and then start working. E.g. 2: The more experience one gains the more one sees that the biggest drag on progress is usually misunderstanding, lack of info, lack of responsibility. So nowadays I do more for my team by creating meeting requests with the right people. For that I need to be able to read all of the source code and docs to figure out where the actual problem is and who really has the expertise to solve issues there. But I don't need to be as good as the topic expert.