Categories
Diversity Technology

Now what was that joke again?

More from the Women in Linux paper:

 

Don’t tell sexist jokes

Sexist jokes are the number one way to drive women out of any group, and they are more common than many people realize. I have more than once heard a man say that he doesn’t make that kind of joke, and then hours or minutes later, hear the same person make a joke about pregnant women or PMS. Sometime he just doesn’t realize that he made a sexist joke, for example, “blonde jokes” are actually “dumb women” jokes. Sometimes he tells me that it’s okay to make a sexist joke if it’s true, or it’s funny (funny to whom?). What some people fail to realize is that jokes about gender of any sort almost always make fun of women, and will make most women angry, regardless of the context. It doesn’t help to first make a sexist joke about men and then one about women.

You can argue that women shouldn’t be so sensitive (and I will disagree with you) but even then, regardless of should or should not, your comments and jokes are driving women away. If that’s not what you want, then don’t make sexist jokes. If you’re not sure if your joke is sexist, find something else to say.

Do protest sexist jokes

The next time you see someone joking about women on your local mailing list or in person, complain about it. It’s difficult to do this without making yourself a target for ridicule, but it’s even more difficult for a woman to do the same thing. Women keep silent when we see sexist jokes because if we protest, we will immediately be attacked for being over-sensitive, uptight, or a “feminazi.” (emphasis added by Bb) (Note: NEVER use the term “feminazi.” It discredits all feminists, and trivializes the victims of the Nazi Holocaust. Consider how ridiculous it sounds to call people like Rush Limbaugh “male chauvinazis” and you may understand why “feminazi” is so emotionally loaded.)

The best way to fight back against sexist jokes is with humor. If someone replies to a post about the technical achievements of a woman with “Is she single?” reply with, “Gee, Jeff, no wonder YOU’RE still single.” Every time a woman sees a sexist joke or comment, she feels angry, left out, and belittled. Every time a woman sees a man stand up against this behavior, she feels included and valued.

Déjà Vu, all over again.

Categories
Diversity Technology Web

The true secret behind the X

Recovered from the Wayback Machine.

Dorothea linked to a power house web site tonight: Women in Linux. You all should print this out on pretty paper, put a bow on it and give it to the Alpha Man in your life.

Seriously, though, Dorothea, I’m finding that this straight forward, honest, and out in the open approach just isn’t effective. I mean, I dabbled a bit with the book, Unix Power Tools, and I still can’t convince people that I know how to turn a computer on, much less work with Unix.

In my experience, every time a woman gets involved in Linux User Groups, or tries to work with Unix in the office, some guy’s going to come along and throw some esoteric stuff at her, making her feel inadequate. And then the dude will walk away, triumphant in the knowledge that he’s prevented women from accessing the secrets of Unix yet again.

So I came up with a plan — a way for women to learn Unix without guys knowing. I told my plan to one of the industry’s leading technologists, and we called the plan Operation X, for the fact that women have two X chromosomes, while men only have one.

Except that when the plan was released, Steve released it as OS X.

And the story goes…

I called on Steve at his home one morning and I started talking to him about the problems women have with learning Unix. I described the put-downs, the deliberate and exclusionary geek talk, the difficulty entering a room full of men and being the only woman present. I could tell Steve was sympathetic, but also distracted. When I pointed this out to him, he apologized, and I asked him what was up.

“Well, Shelley, the point is that Apple isn’t doing that great at the moment. We keep losing business market share to He-Who-Must-Not-Be-Named, and the geeks think the Mac is a frivolous operating system that’s far too pretty and friendly and helpful to be taken seriously.”

“Wow, Steve. I didn’t know things were that rough.”

“Yeah. I’m down to my last few billion.”

“Bummer.”

“Yeah. Bummer”

Then I had this epiphany! Excited, I turned to Steve and said, “Steve! I have a great idea!”

“Shelley, I’m sorry but I’ve told you before — I’m not going to incorporate RDF/XML into AppleScript.”

“No Steve, not that idea. A new one!”

“What is it?”

“Well, you say you want to attract geeks, right?”

“Right”

“But I imagine you don’t want to go with Linux or something like that cuz that’ll scare the corporate types, right?”

“You got that right. I can imagine going into Citicorp with Linux of all things.”

“Sure, sure. I know what you’re saying Steve. But what if you hid the Unix?”

Steve was puzzled. I could tell. Most people couldn’t, but I could tell.

“Come again?”

“Well, Steve, you use Unix for the base of a new operating system, but you put the old, familiar, less intimidating Mac stuff on top to hide it. With this, you can sell the OS to the corporate types — see no geeky Unix hacker shit — but still attract geeks because underneath all that puff lies a Real Operating System.”

As I was talking I could see Steve warming up to the idea. He said, “That’s a great idea! Shelley, that’s an incredible idea!”

He started pacing about, gesturing excitedly with his hands.

“We could develop new, flashier graphics — call it ‘clouds’, or ‘glitter’, or something with marketing clout like that. And we could incorporate bits of open source in with our commercial stuff and the uber-geeks would get off our butts about proprietary hardware.”

Steve rambled on for a while, fleshing the idea out. Finally, he started to wind down, and turned to me sheepishly.

“Shelley, you really saved my butt, but you came to me for help and I haven’t helped you at all.”

“But Steve you have”, I answered. “Once the new operating system hits the street women will be able to learn Unix, finally, without men knowing about it.”

“How come?”

“Here’s the scenario: a woman is working away in the Terminal, typing ‘nix command after ‘nix command, but then a guy comes up and asks what they’re doing. The woman quickly collapses the terminal, hiding what they’re doing, and shows the guy their drawing, or graphic, or letter, or whatever they’re working on. Non-threatening stuff.”

Steve’s quick, because he responded with, “Learning Unix with stealth technology. I like it!”

So we hashed it around, coming up with the name and all. Later, as he was seeing me out, I happened to notice a laptop computer by the door and asked Steve what it was.

“Oh, it’s a new computer case we’re working on. It hasn’t been painted yet because we’re trying different types of paint to see which works the best.”

“I don’t know, Steve. I kind of like the bare metal look myself.”

And there you have it. The truth behind OS X.

Really, really.

Categories
Diversity Technology

Coders-only-club strikes again

Recovered from the Wayback Machine.

Catching up on reading tonight, I stumbled over the following at Mark Pilgrim’s:

 

On a side note, remember that flap just before the holidays about the Coders-Only Club? Well, look at it this way: some people have strong opinions about the way computers should work. Other people have strong opinions about the way computers should work, and back them up with code. It seems obvious to me which people deserve more attention. Maybe that’s just me.

Since this was addressed to little ole me, I thought I should respond.

What can I say Mark? I don’t throw a lot of code around here abouts, primarily because I’ve been saving most of it for the book. Hard as this is to believe for some folk, especially employers in St. Louis, writing a computer book is quite difficult. Especially writing a book on a specification that’s changing, constantly, and working with technology that’s in beta — if I’m lucky.

However, as additional credentials, you all can help yourself to the resume in the upper left-hand corner and take a peek; you’ll see that I’ve thrown my mind around a line or two or 100,000 of code.

It also seems to me, though I am getting older and my brain’s been rattled a tad by the falls, as if I have thrown out code a time or two in this weblog, including a new version of RDF/RSS and other odds and ends. Seems to me that most of technical gentlemen hereabouts didn’t take all that much notice of the little woman and her bits of code. Kitchen things.

(Hey! Isn’t SOAP a kitchen thing?)

Seems to me that some people have put me into a box and are now wrapping that box with a bow and then dismissing me without due consideration, because I don’t put code into this here weblog. But you know, I really don’t like bows, and I really don’t like being clapped into a box. And I really haven’t mastered the skill of pissing standing up so I’ll forgo pissing contests if you don’t mind.

If, and when, I put code out at this site it will be because I want to, for fun, for interest, to help others — not to ‘prove’ something to anybody. And if you want to get into a debate, then you all might want to consider judging a person on the merit of their words, not the elegance of their regular expressions.

Categories
Technology

Apple’s open core

As happened last year with the Macworld conference, you might as well bag writing about anything else because this week will be Apple, Apple, Apple.

Two big stories — a newer, longer TiBook and Safari, Apple’s entry into the browsing market.

I liked some features of the new TiBook such as the backlit keyboard, which I think is one of the best ideas I’ve heard with a laptop; I know I wish I had this with my TiBook. However, I’m less impressed with the length of the TiBook — 17 inches. My 15 inch works nicely, I drag it about the house and everywhere I go with no effort. All that extra length with the new TiBook does is make it too long for most computer carry bags. Heck, it’s too long for most laps.

What Apple needs to do is incorporate all the other goodies into its 15 inch model. Including the airport, Bluetooth, the graphics card, and that nifty backlit feature. That would be a tasty morsel, and I’d be putting up a PayPal donation button to have you all buy it for me.

And the Titanium PowerBooks are still the sexiest computer on earth.

An even bigger story is Apple’s release of the new Safari browser, which I don’t think is a huge surprise, was it? The best place to get a re-cap on all of the excitement is over at Mark Pilgrim’s. He did a nice first review of CSS support within Safari, and links to others who also reviewed the browser. Better yet, everyone else interested has linked to him and they’re all showing up in his referrals. Sticky Strand technology hits again.

I tried Safari and didn’t have too many problems. My weblog is quarked, which makes sense — automatic resizing of table columns that don’t contain any data, such as my outer columns, almost always looks bad in beta browsers. I also tried the browser on my more markup savvy weblogging neighbors such as DorotheaJonathonAllan, and Mark and their weblogs look great. I guess there is somthing to be said for all that they’ve been trying to teach us this last year.

If you don’t have a Mac OS 10.2 equipped machine, holler and I’ll take screenshots of your weblog with the browser and email them to you so you can see for yourself how your pages look.

Despite of all the hooflah about the TiBook and Safari, I was more interested in seeing additional examples of Apple’s unique and successful blend of open source technology paired with commercial interests. Steve Jobs has an uncanny ability to mix the two and have it work. Timothy Appnel captured the essence of Safari and it’s impact on open source when he wrote:

 

Apple’s use of the Konqueror/KHTML rendering engine as opposed to Mozilla Gecko is a bit controversial (or more accurately intruiging), but in the long run will be beneficial to the space. Instead of one open source engine, developers will have more choice and the inheritent flexibility that two different efforts provide.

I agree — two open source engines are better than one. I know it’s going to be a hassle, and we have yet another browser we have to test against with our web pages. However, competition is good — do you want to be stuck only with IE?

The browser’s interesting, and the computer’s sexy, but the top story for me is Apple’s release of an X11 Windows system for Mac OS 10.2. It’s based on the XFree86 project, just like XDarwin, the most popular X11 for Mac OS X at this time. Again, an effective blend of open source and commercial use, and increased competition among vendors.

Apple may have added entries for both the browser and the X11 markets to their stable, but they left the barn door open and anyone with a keyboard and an inclination can trot in and hunker down at the same oat bin.

Categories
Technology

Tiny Steps and Big Leaps

Recovered from the Wayback Machine.

Challenged by Clay Shirky, Ben Hammersley has created a special post to collect trackbacks related specifically to the LazyWeb.

What is the LazyWeb? Well, do you have an idea and need help with technical implementation? Do you need specific functionality or an application or utility, but you’re not a coder? Capture the idea as a LazyWeb request and ping Ben’s special site. Chances are the request will be filled before the ink is dry on the page.

Ben’s idea, a demonstration of LazyWeb in action, is great. I agree with Poetic Geek’s delight in the concept, though I’m not sure that I’m “…giggling with girlish delight” over it.

I think we’re seeing a new form of open source development, based on technology developed for the community and its immediate, expressed needs. A case of community searching for technology rather than technology on the hunt for a users.

I would like to see additional efforts associated with this. For instance, it would be great if people would flag weblog posts that provide solutions for LazyWeb requests, or that provide technical help, especially within the weblog community. A case in point is my MT Comment How-To, further refined by other contributions in the comments. By isolating these items we can begin to build online technology centers that are anything but centered — true distributed technology, and true distributed technology documentation. There are just some things that shouldn’t roll back into the dustry reaches of the archives.

Perhaps Ben can stretch his LazyWeb post to a complete LazyWeb weblog, tracking LazyWeb implementations and providing a focal point for this effort in 2003? Not that I’m volunteering Ben’s time, and I am more than willing to volunteer to do this myself if Ben would rather. After all — we want to track fulfillment as much as request.

Additionally, I would also like people to start putting their code online. This last week there was a great deal of discussion about the CITE tag and how it can be used to provide specialized processing. Well, that’s great and good, but let’s see the processing? Can we see the code that Mark used. Or Sam’s code? I played with CITE a bit and created some code, which I then packaged for people to download. Not great code. Maybe not even good code. But at least it’s there if anyone wants it.

For instance, the code allows me to reach into Ben’s new LazyWeb RDF/RSS file and pull out existing topics and descriptions, as shown here.

There. I guess that’s my LazyWeb request — put your code online, let us take a peek. We promise if we shoot ourselves with it, we won’t blame you.