the meeting:: inception
I had a meeting a couple of weeks ago, with some people in myCompany's Marketing group, along with some folks in myCompany's Customer Relations group. See, it seems that some users (external customers) weren't happy with some of the development that we'd done in a previous release. Well, not happy isn't really a strong enough word - the Marketing manager was pretty f***ing pissed, and had raised enough hell to warrant getting several application teams together to allow him to properly vent about it.
the background:: framework
If y'all didn't know this by now, I'm a web developer. Programmer by title, Java developer by trade, although I've dabbled in a lot of different technical roles (content developer, technical writer, coordinator, etc). Oh yeah, and if I hadn't mentioned it, I'm black. And female. And a rarity in my field.

See, in a department of about 120 or so odd "developers", I think there are about 4-6 of "us" black women. Most of whom are either currently-in or consciously-being-steered-toward less-technical roles: content developer, coordinator, quality assurance analyst, functional analyst, coordinator etc. And even if you widen the net, and include black males, still...there's maybe 12-16 of us. That's not quite 17%, is it?
And to some extent, we all face similar challenges. Our technical skills are always in question, we have to work twice as hard just to keep pace with our counterparts, and because of globalization, the playing field just took a new slant. Why hire African-Americans, when you can hire people of color that are culturally perceived to be more technically adept, or from areas of the world whose pay scale is much lower than that in the US? Ok, I'm not even going to attack the out-sourcing issue - I just want to note how it colors my environment.
the meeting:: revelation
But back to the meeting: my project lead's called to task by her boss about this issue, so a meeting is called to address the problem (and get Mr. f***ing pissed off along with some of myCompany's other bigwigs to back off). Us peon technical folks are called in to explain to the less-technical bigwigs why we can't do what Mr. f***ing pissed off wanted us to do.

I arrive a couple of minutes early, and Mr. f***ing pissed off is already there, along with a couple of his underlings, one of whom is black. I subconsciously smile, because in an environment where we aspire to be 10% of the working population, it's always nice to see a similar face. My boss arrives next, as do four of my teammates: TC, KC, KF and WB. Now, TC leads off, as usual - he's the technical lead, and when I say he's well-versed don't take me at my word. He's forgotten more code than I've yet to write. To the techies reading, he can quote large sections of the Java API off the top of his head, which to non-techie folks is like not just quoting the bible, but being able to debate Pat Robertson (ok, insert some other sane religious icon here) about the actual original Arabic transcription. Dude is that good. Then he calls on KF to explain her piece of the application, and she does her thing in technical terms. When Mr. f***ing pissed off does his Scooby-Doo impression ("ruh-roh?"), KC breaks this into layman's English for him, giving the issue a business perspective. Mr. f***ing pissed off asks me about my portion of the application, and I give him the spiel in (relatively) non-techie speak about my piece's limitations. WB is (as usual) silent, instead allowing the more seasonsed developers to take the lead in this meeting. My boss asks if Mr. f***ing pissed off is satisfied, which by this point is a gross understatement: Mr. f***ing pissed off is actually happy that we did what we did, which is really more than we should've. My boss ends the meeting and we return to business as usual.
What makes this whole thing unique is the cast of characters:
my Boss: black woman
TC: black man
KF: black woman
me: ok, you know the deal
KC: Japanese woman
WB: white man.
Mr. f***ing pissed off: c'mon, you already know the answer to that one...
the meeting:: reality
The whole time we're in that room, what's really going through my head is: we're handling biz. We're handling biz. This dude (Mr. f***ing pissed off) probably talked to a couple of us individually, and thought to himself - "I don't think they know what the h*** they're doing". But we came in that room and handled biz, so that he couldn't do jack but say to himself "dayum, they did a good a$$ job, considering the circumstances". That, my fine blog-reading friends, warms my code-writing, take-no-prisoners, cold-to-the-politics-of-big-business heart.
the social network:: facilitation
We've formed a loose network of colleagues at work, based not just solely on race, but also on similar interests & skills; and we network, as well as help keep each other apprised of some of those "silent" developments that go on in the workplace. We help each other with code, we validate/invalidate office gossip, and we try to "stick together" as much as can possibly work, in this dog-eat-dog world. The most important part though, is that we've realized we have a greater impact collectively, than most of us individually can imagine. Which is antithetical to corporate culture and survival.
A policy of inclusion is what most corporate consciousness sorely lacks, and is what makes this loose collective strong. We don't all "get along". Some of us can't stand others of us, on a very personal level. And there's always others of us that are just "extra", and can be pretty hard to swallow. But no one is "excluded", unless they choose exclusion themselves. And that's ok, because no individual can take away what truly belongs to the collective. Even if one person leaves the group, another takes up their place, learns something in the process, and the collective grows.
the cultural reality:: departure
I admire my colleagues a great deal, because of their skills and the unique abilities they bring to the table. Despite my at-work introversion, I've tried to immerse myself in this "collective", to learn as much as possible, in the short time I have to be around them. Some of us will leave myCompany, some will stay...some will remain tight, and others will drift apart. The bottom line is that we've all grown as part of this experience.
That's my paradigm of diversity. Somehow, I hope myCompany catches on, the way Mr. f***ing pissed off did. And I hope myCompany catches on while any of us still care to show it.
sidenote:: myBoss and TC are on their way off to other projects, to be replaced by demographically sterotypical developers. This saddens me a great deal, because I like and admire both of them, and it's been a great pleasure working with them, and learning from them.