The worst manager I've had, tried to often pretend he had any idea what he was talking about when pitching some gibberish during the 10min standup talk. He would often make suggestions like "and if you use Apache Solr? ". My face would be like ":/" and had to explain a subtle no (cause he was paying my salary). If he wouldn't be putting up that act, and just work the team dynamics without trying to provide technical solutions to experienced coders who will be like ":/", he would actually fare pretty well I think.
But I must say if you are presented with a tough technical problem, and human resources to solve it, but you fail to comprehend the problem and how you should direct your resources in solving it, it's going to be a tough cookie to make any impact other than wasting your time, and precious developer hours trying to do something you can't.
The best one I've had I worked with for a long time as a colleague freelancer, and 0 hour contract directly under him until we expanded to a 15-20 workforce.
He was an experienced PHP'er, and would argue even a better salesman and networker.
He would almost never write any code, but when push came to shove he would provide the fix within minutes time after a client made an upset call after hours.
Most importantly: Other than being able to point out strength and weaknesses of his employee's, he was never afraid to acknowledge his own, and always assumed our expertise over his. ( unless someone really f'd up of course :) )
But I must say if you are presented with a tough technical problem, and human resources to solve it, but you fail to comprehend the problem and how you should direct your resources in solving it, it's going to be a tough cookie to make any impact other than wasting your time, and precious developer hours trying to do something you can't.
The best one I've had I worked with for a long time as a colleague freelancer, and 0 hour contract directly under him until we expanded to a 15-20 workforce. He was an experienced PHP'er, and would argue even a better salesman and networker. He would almost never write any code, but when push came to shove he would provide the fix within minutes time after a client made an upset call after hours. Most importantly: Other than being able to point out strength and weaknesses of his employee's, he was never afraid to acknowledge his own, and always assumed our expertise over his. ( unless someone really f'd up of course :) )