I sent a girl friend of mine a link to that article about Britney Spears not knowing who Yoko Ono is. It turned into a big argument about me being arrogant thinking that everyone should know what I think they should know. I said, that if someone perpetuates a perception of being passionate about something, that there are certain things that people should know. My examples (she's a coworker, and I'm a developer, so these examples made sense)...
If you're a Perl programmer, you know what "the camel book" is, and you know who Larry Wall is. If you don't, how the hell could you really be a Perl programmer? You may hack out a few lines of code, but you haven't spent much time really learning about your language.
If you're a Java programmer, you know who James Gosling is. How could you not?
If you're a C programmer, you know what the K and the R in K&R mean, and you know their names. More likely than not, you have read K&R, and might even still own a copy. There are *constant* references to K&R in the C world, so if you've never even heard of it, your background is questionable.
If you're a Windows programmer, you've probably at least *heard* of Petzold, if not read him.
If you do MFC, you at least know of Prosise.
If you've done any research into Windows internals, you know/read Richter.
I offered many more arguments, not all relating to development, but it was shortly after that point that I somehow gave off an arrogant vibe, consequently leaving me talking to myself. Am I way off base? I think it's this way with anything. If you're interested and involved in something, you'll always pick up idioms that only someone else of the same interest would understand. This may not be a way to immediately disqualify someone as being truly a pundit, but it definitely gives a heads up.
Sorry for the long post. Thoughts?
If you're a Perl programmer, you know what "the camel book" is, and you know who Larry Wall is. If you don't, how the hell could you really be a Perl programmer? You may hack out a few lines of code, but you haven't spent much time really learning about your language.
If you're a Java programmer, you know who James Gosling is. How could you not?
If you're a C programmer, you know what the K and the R in K&R mean, and you know their names. More likely than not, you have read K&R, and might even still own a copy. There are *constant* references to K&R in the C world, so if you've never even heard of it, your background is questionable.
If you're a Windows programmer, you've probably at least *heard* of Petzold, if not read him.
If you do MFC, you at least know of Prosise.
If you've done any research into Windows internals, you know/read Richter.
I offered many more arguments, not all relating to development, but it was shortly after that point that I somehow gave off an arrogant vibe, consequently leaving me talking to myself. Am I way off base? I think it's this way with anything. If you're interested and involved in something, you'll always pick up idioms that only someone else of the same interest would understand. This may not be a way to immediately disqualify someone as being truly a pundit, but it definitely gives a heads up.
Sorry for the long post. Thoughts?