+1, I'm with you on this :) I'm also like OP and you: partly creative, party technical (but very broad, I'm not a hardcore developer with a speciality) and do have business and social skills too. So I'm at the end of my 20's and working as a Technical Project Manager... which I enjoy so far.
I was pretty much like the OP (from Georgia Tech too), although I graduated with a masters in CS, so I had that to back me up at interviews. I hated programming as I worked at companies large and small writing code in java (mainly tweaking spring configs) and have spent the last few years trying out for different product management positions with no luck.
I realized that I did not like it much, was because I was fighting the system every time as I did not have the basics right. (I barely could get myself round a linux box). I have since made it my priority to get my fundamentals right and started reading the basics of everything as if I was getting into programming from scratch. I feel it has helped.
Also it happened that my current job required me to learn to code in python. Ever since I started working in python coding has been very pleasurable and fun. Also the ability to quickly have an impact and be useful gives me the thrill rather than just writing a bunch of integration tests.
Anyways Im not sure why this is relevant, but felt like putting this out anyways.
I have not read much in regards to WHY this exact same bug was also found in OSX. Can anyone shed some light on this?
Do they use the same code stack for iOS and OSX? This seems weird to me - even though parts of code could be used in both operating systems, I would imagine separate teams would be on iOS and OSX, each reviewing code bases on their own, running unit tests and whatnot. Still, this major flaw has been present for 2.5(?) years - all the more reason for paranoia about its presence.
Add to this, why wait so long with the OSX update? A security issue THIS serious MUST be patched instantly and rolled out as an individual/separate update as soon as possible, even if that means pushing back OSX 10.9.2. Or did they need some time to introduce a new flaw somewhere? o_O