Why I'm learning to code - Roy Bahat, President at IGN Entertainment
I was in a medium-sized company where the VP of Engineering started attending design meetings.  Talk about a huge waste of time and a huge distraction.<p>Because he was the VP, and kind of jerk at that, everyone acted differently in the design meetings but everyone felt compelled to answer his questions because he was the VP.  He would ask obvious questions that would derail the entire process.  It was completely unproductive, but he really felt he could "add value" by attending the meetings, but it was pretty obvious that his expiration date as a technical person was long gone.<p>There was a funny quote a few weeks ago about how Zuckerberg wanted to go in and fix a few bugs and developers were complaining because he was way slower, etc, and basically just interfered with the process.<p>I'm glad that the original author is interested in learning how to program, but if it means he's going to stick his nose in and start gumming up the system, then he should stop.  Programmers require a certain personality type.  You can't take someone in sales and think that by understanding programming that it will somehow help him.  Leave the managing to the managers, leave the sales to the sales people, and leave the programming to the programmers.