Ex-director-y, Part 10. Myers Briggs for Programmers

I just found an article relating Myers Briggs For Programmers. Quite interesting, if you like stuff like this (which I confess I do: I automatically try to 'type' everyone I meet!).

There are a few points of interest to me (as an ENTJ):

1. As an E, I shouldn't really be working alone. It's true, I do struggle sometimes, and often talk out loud to myself!
2. The Author couldn't easily relate F for programmers, which from my experience doesn't matter: few programmers are F!
3. J's would tend to prefer C++ to Smalltalk (or Ruby), because they need to fully understand things. I would tend to agree that I found Ruby almost too powerful at first, asking myself how it could possibly do some of the things it does. P's wouldn't care; they would just use the power. How did I cope? I wasted loads of time finding out how Ruby (and Rails) works!
4. Very few (software?) workplaces have high N. I have experienced this too (much to my frustration). S's will tend to resist change, opting for tried and tested approaches, or the quickest (not necessarily best) solutions. This might be OK for business in the short term, but there is a risk of falling behind more progressive N companies, who define bolder goals and invest to achieve them. As I've mentioned previously in my Ex-director-y posts, I wish I'd been tougher on this, but I wasn't and that's why I had to go...
5. I'm gratified that Google is ENTJ, and Microsoft is ISTJ. This makes complete sense to me. I have looked inside a few low N, high S led organisations and the most frustrating thing for me (as a strong N), is that it is exactly an S quality not to appreciate the need for some N, which leaves them floundering about in the present rather than moving towards a future. Microsoft obviously hasn't always been an S organisation, but it clearly is now, so was Woolworths.
6. I'd most like to work with an N-F, to blend their wacky with my mighty.