..Once upon a time I wanted to be an electrical engineer.  I would design the next generation computer CPUs. A job at Intel or Motorolla.

But somewhere along the way I ended up writing some game for OS/2. I didn't even know how to program at the time. I bought "Teach Yourself C in 21 days" and a couple OS/2 programming books and wrote a game.  I didn't get actually paid for that game because the publisher ripped me off. Took the money and ran. So fine, I would write software and publish it and also publish the software for other software developers so that they didn't have to go through what I went through.

But to do that I would need to bring in other people to help with that.  Marketers, sales people, managers, relationship managers (what the hell is that?), an dother people. And of course, OS/2 died off (unless you're one of the freaks who hangs out on comp.os.os2.advocacy still) so then we had to move to Windows so I had to become a financial management guy too as we migrated.

Over time, I slowly found myself not writing very much code but managing these dozens of people.  Next week, I am going to schedule some time to write some code for one of our products.  I may get to spend a total of 16 hours next week writing code! The rest of my time I'll be grumpy old man walking around the office cranking at people for not doing what they do as fast or as well as they should.

The moral of the story is that electrical engineering is not a good background for managing people. Though it will teach you how to design the perfect electrical whip...