Making invisible patterns , visible

Which is more useful- Being a specialist or a generalist? Which is more satisfying personally ? This question came up when a friend was pondering on what to focus on next in terms of career choices.  This issue often comes up for middle managers(generally highly paid) - who are suddenly faced with an interruption in assignments. Self doubt creeps in when they realize that they do not seem to have a personal area of expertise. That all they seem to do is prepare and review office documents - and spend time in meetings and conference calls.  They know that being a 'techie' does not pay , and yet meetings and documents do not seem to be particularly valuable contributions to the betterment of mankind. Better paid cog in the machine!  So in deciding what to do next - ie specialize or remain a generalist- and to derive more satisfaction from your work- you need to visualize your purpose and role in the network - to better understand your contributions.  First and foremost

The other day - I was nursing some inflamed tendons in my left knee. The result of a 1000 mile drive from Boca Raton to Alexandria VA - and an immobile left foot for hours! As I was waiting for the doctor, I was studying the colorful diagrams of muscles and tendons and bones and their connections. Of course the nerves that actuate the systems are not shown in the charts. As the doctor started his diagnostic process and pressed down on the knee and pain shot through it - it got me thinking and marveling about the nerve sensors and 'inbuilt' feedback infrastructure that nature builds into animal bodies - to protect it from damage. I could not help myself contrasting it with our code writing as we build systems. We don't always put 'diagnostic' sensors everywhere as we go along(laziness?). But nature does not forget to do that. It unfailingly builds feedback sensors into all the muscles. I wonder why. Does it have an evolutionary benefit? Would it not be benefic