I think a big part of the problem is that a lot of folks who are okay at programming but not really really good get into positions of power one way or another and then sort of gum up the works.
Story time...
I worked (briefly) at a large company that had hit hard times and then found new investors, so most people had left and then they were hiring new folks (like me.)
One meeting the CTO comes in and sketches out his idea for our new infrastructure on the board and, lo and behold, he's reinvented ethernet.
My immediate supervisor gave me a piece of code he had written using a state machine. You know that feeling when you read some code and it's like "am I an idiot or is it this code?" The state machine graph was:
A -> B -> C -> D
He used a FSM library for this. I replaced it all with about ten lines of code and bounced it back to him. I got the feeling after that that he didn't like me, but wtf am I supposed to do? Dude's my boss but he doesn't know what a state machine is.
(I was ready to quit, talked to HR on Friday, Monday they laid me off. Bullet dodged IMO.)
Story time...
I worked (briefly) at a large company that had hit hard times and then found new investors, so most people had left and then they were hiring new folks (like me.)
One meeting the CTO comes in and sketches out his idea for our new infrastructure on the board and, lo and behold, he's reinvented ethernet.
My immediate supervisor gave me a piece of code he had written using a state machine. You know that feeling when you read some code and it's like "am I an idiot or is it this code?" The state machine graph was:
He used a FSM library for this. I replaced it all with about ten lines of code and bounced it back to him. I got the feeling after that that he didn't like me, but wtf am I supposed to do? Dude's my boss but he doesn't know what a state machine is.(I was ready to quit, talked to HR on Friday, Monday they laid me off. Bullet dodged IMO.)