My comments are referencing people who like to be hands on, and not people who always wanted manage and coded just because they had to. As you get more experie

My comments are referencing people who like to be hands on, and not people who always wanted manage and coded just because they had to. As you get more experienced you 1) Get better/faster at recognizing when a project will fail for non technical reasons. Software is one of those fields where somebody who likes coding can feel like every problem is solvable with technology. As you get more experienced, you get better at seeing the non-technology aspects of a problem and when a non-technology aspect is going to support or hinder the success of a project. 2) Developing a desire to deal with non technical aspects of project. Not because you "have to" but because there is the realization that a good/satisfactory solution to a business problem will never occur if you don't take some ownership in the decision making process. This also helps you be more interested in what you are doing because your view of the world is not just a bunch of project documents, tickets, and echo-chamber internal meetings.