Categories
Technology

Hello iPhone

Amidst all the hype surrounding iPhone, one thing is very clear: the iPhone will have some impact on web site development. At least, for those sites wanting to attract a well-to-do, gadget focused community. Or I should say, among those who are well-to-do, gadget focused, and who don’t have long fingernails.

The iPhoney emulator provides a means to test your site or web application in an iPhone environment, without having to shell out the money or sign up for two years of service at AT & T.

Apple has also, sort of, kind of, provided development guidelines. The company stresses making content ‘double tap’ friendly: blocks of text, sized just right. You’ll have to decide how much of your site you want to make ‘double tap’ friendly, and whether attracting iPhone users is worth the extra effort.

West Civ has done a more detailed look at the design specs for the device, and points to a Google Group related to the product (via Virginia DeBolt).

Ajaxian has created a whole new category devoted to iPhone development. GigaOm asks Where are the games?. Why, right here: Pick-a-Pair small gameMedium Game, and Triple card game. These are image match games based on technology close to 8 years old (JavaScript/HTML) that I updated to use with the Flickr recently loaded image queue (accessible via the API). I thought the games might work with iPhone, and according to iPhoney, they do.

I feel so über hip, now.

Before rushing off to hack the black, one thing I take away when reading Apple’s developer material is that the company doesn’t necessarily want people building overly complicated, special purpose iPhone applications; or, at a minimum, applications that make torturous use of any possible hacked entry into the device. The stress is on small image and script files, clean scripts, fast application execution time, and fast loads. If you build an application on an undocumented hack, don’t be surprised to find that door slammed in your face next software update.

Apple wants control with this device. Keep that in mind when you spend your time on finding those clever ‘workarounds’.

Categories
HTML5 XHTML/HTML

Marathon 2.0

I must admit to being confused about Molly Holzschlag’s recent posts, including the latest. Today she writes, in clarification of her post where she calls for a moratorium on new standards work:

Perhaps there is a better solution than pausing standards development. If so, I’d like to know what you think it might be. One thing is absolutely key and that is there is no way we are going to empower each other and create the Web in the great vision it was intended to be if we do not address the critical issue of education. And stability. And these things take time. It requires far better orchestration than I personally have been able to figure out, and while the W3C, WHAT WG, WaSP and other groups have made numerous attempts to address some of these concerns, we have failed. We haven’t done a good job so far to create learning tools and truly assist the working web designer and developer become informed and better at what he or she can do. We haven’t done a good job sitting down at the table together and coming up with baseline strategies for user agents and tools.

I don’t keep up with the daily effort of the WHAT WG group, because I’m not really a designer by trade. I do keep up with specifications once they’re released, and am acutely aware of the necessity of valid markup, and not using worst practices (I promise to stop using STRIKE, for instance). I’m also aware of accessibility issues, though I find it frustrating how little we can do since many screen readers just aren’t capable of dealing with dynamic web pages.

I do try to keep up with the JavaScript effort. Mozilla is usually very good about providing readable documentation of new advances, and though it is typically ahead of the game, at least I’m aware of what’s coming down with the road. The same with what’s happening with CSS, PHP, RDF, and other technologies and/or specifications I use in my development.

If there are perceived barriers in acquiring the necessary knowledge to work with the newer specification, it can be because people heavily involved with some of these efforts can come across as arrogant, impatient, and even intolerant–the ‘elitist’ that Molly refers to. Over time, though, such ‘elitism’ usually gets worn away. I used to think the people associated with RDF were elitist, but I’ve watched in the last few years as folks interested in RDF/OWL/semantic web fall over their own feet rushing to increase understanding of, and access to, the concepts, specifications, and implementations. Express even a mild interest in RDF and *whoosh*, like the debris left by a flood, you’ll be inundated with helpful suggestions and encouragement.

Issues of arrogance and elitism aside, the concept of halting effort on specifications while waiting for the rest of the world to catch up just doesn’t make sense. Yes, it can be overwhelming at times–CSS, HTML, XHTML, XML, RDF, DOM, ECMASCript, PHP, Ruby, etc, etc etc. So much to absorb, so little time. But that’s not going to change by halting work on improving and extending specifications.

We do need to have more consistency among the user agents, such as the browsers. But we have browsers now that don’t implement, properly, specifications that have been around for years. In fact, it is because of this that we have this alphabet soup, as we try to remember which browser handles which piece of which HTML specification, correctly. Don’t even get me started on how user agents handle JavaScript. Or CSS.

I don’t know much about the intimate details of the HTML5 process, other than the whole point of the effort was to bring about a common point on which we could all intersect–authors and developers in what we use, user agents in how the implement the the specifications. Once this place of mutual agreement is then reached, we can continue to move forward, each at our own pace. It doesn’t make sense, though, for all to stop moving forward because some developer in Evansville, Illinois, or Budapest, Hungary, is still holding on to their tables.

Consider a marathon. In marathons, all the participants have to agree on the rules, and have to make sure they’re following the same course. But once the rules are defined and the course is laid out, then it’s up to the individual participants to do what’s necessary to complete the course. Some people put in more time and training and they complete the marathon sooner than others who can’t put as much time in, or who perhaps don’t have the same level of physical conditioning. Most of the people that participate, though, don’t care that they aren’t first or second or even in the first hundred. Most people have their own personal goals, and many are happy just to finish.

Think, then, how all participants would react if those putting on, say, the Boston Marathon, were to tell the participants that those in the front needed to slow down, or stop, so that those in the back could catch up?

The web is like a marathon. The specifications define the rules, and the implementations define the course. It is up to the individuals to determine how fast they want to run the course.

Molly says, because a developer in Evansville, Illinois or Budapest, Hungary is still using HTML tables for layout that the web is ‘broken’. I think what she’s really saying, though, is that the web works too well. There is a bewildering wealth of technology we can pick and choose from, and it can be both intimidating and exhausting trying to stay aware of all of it, much less stay proficient in any of it. It also seems like we’re surrounded by people who know it all.

They don’t, though. No one knows it all. The same as no one runner wins every marathon. None of us can know it all, and none of us can afford to be intimidated by those who seem to know it best.

No matter what we do with web specifications and new technologies, there will always be those who push to be first; the expert, the most knowledgeable–the ‘leader’ if you will. Then there is the rest of us, doing our best. This state of affairs is not broken, it’s just the way it is. It’s OK, too, because we don’t need to finish the race at the same time. What we web developers and designers need is what the marathon runners need–a set of rules by which we all participate, and a consistent course on which to run.

And here I got all this way without once mentioning Microsoft and IE.

Categories
Diversity Technology

Where are the jobs? Where are the opportunities?

Recovered from the Wayback Machine.

As is typical for events such as these, mention is made in comments related to the “Beautiful code” book about providing a list of women–the typical “where are the women” these discussions always break down to. How many times do we have to do this? And in how many places? Are these genuine questions? Or just a convenient way to put the burden of the lack of diversity back on we women?

A better way of looking at this is, where are the jobs? Where are the opportunities? Where are the companies that genuinely want to hire more women in technology because they want to diversify their workplace? Where are the editors or conference givers who want to provide a richer experience by ensuring a balanced offering?

What we need is to start building a list of companies who are actively recruiting women techs. The same for conferences and books. Then we can publish these, with requirements, location, and other information, and let the women who are interested come to you–because you sure as hell are not coming to us any time we build yet another list.

If you think diversity is important, and you’re hiring, let me know and I’ll publish your job. I’ll put these into a separate category so that women can search on jobs, and close the job post when the position or positions are filled.

If you think diversity is important, and you’re looking for an author, writer, or conference presenter, let me know and I’ll publish a post about your book, magazine, or conference. Again, I’ll put this into a separate category so that women can also search on writing and presenting opportunities. If your conference speaker list closes, or you find the author of your dreams, I’ll close the post so you won’t be bothered, and the item no longer turns up on the active list.

Yes, I could create a wiki or an application and do the same thing, but that’s focusing on the technology; focusing on the technology has not worked once in the past. Enough with focusing on the technology, time to focus on finding a solution.

So, where are the jobs? Where are the opportunities for women?

Categories
Diversity Technology

Women evidently don’t code

Recovered from the Wayback Machine.

If you’re an older woman in tech you’re faced with a double whammy. In the last post, we discover we’re too old to ‘hack the web’. However, we’re also not considered much of a programmer, either. Or at least, that’s what I read from the table of contents and authors for the new O’Reilly book, “Beautiful Code: Leading Programmers Explain How They Think.”

Out of 39 authors, only one is woman, and she’s a co-author of one chapter.

Way to set a real high standard, there, O’Reilly. What can I say? When O’Reilly raises the bar on diversity, the call goes out for Limbo!

Disclaimer I have written several books for O’Reilly, and am currently working on a new one.

update

The organizer of the book stated (in comments, email, and post) that he contacted 15 women to write an article for the book, and only one responded affirmatively. He contacted 130 men, and 37 accepted–giving an acceptance rate for men was about 25% (I show 28%), and for women, about 6%. I would imagine since the invitations were based on how ‘well known’ and ‘popular’ the person is, the list of women invited would include the same women who are always invited to participate in these events. This probably accounts somewhat for the lack of time to be involved in a project–I don’t know, the names of the women were not divulged.

I am disappointed that more of the women didn’t participate. I’m even more disappointed if none of those who could not participate didn’t bother to recommend others in their place–heavily disappointed in this one. But I’m also disappointed that O’Reilly didn’t work with the book organizer to attempt to contact other people who might have helped the organizer determine other good candidates.

The number of men invited was 130, women 15. This means the invitation rate for women was 11% that of men, which is a small pool on which to depend. If we look at the topmost 10-11 percent of men invited (based on the same criteria of popularity as applied to women), would we still have the same 25% acceptance rate? Hard to say, because again, we don’t have all the data to extrapolate true knowledge.

I do know this: even doubling the number of women invited may have driven out 2 or 3 additional women. Not many women, true, but at least the lack of women wouldn’t be so painfully obvious. The acceptance ratio might even have been higher, if the pool of available women is extended beyond the same criteria used in every other event of this nature.

The result of this small additional effort would be that not only would women in technology have felt we achieved some fair representation in the book, the work would also have provided a more diverse point of view, and thus been a richer book. But what was it that was written in comments to this post?

While they could make an awesome book, of course, with a more diverse quality of authors, but that is not their priority; it is a waste of time, in my mind, to spend time trying to find someone of a certain gender or race, when one could get a similar result without all that effort.

The organizer of the book accepts full responsibility, but I’m not letting O’Reilly off the hook. The company knows that this is an issue that arises time and again, and should have been sensitive to such and worked with the organizer. Now, what we have is a reaffirmation–yet another reaffirmation–that whether women in tech are represented or not just isn’t that important; that working towards such is ‘not worth all that effort’.

You know what’s sadly ironic about this? The author royalties (not company profits) from the book go to Amnesty International, an organization I strongly support primarily because it is one of the few that won’t compromise when it comes to fighting for the rights of women.

Categories
Diversity Technology Web

Speak softly

Recovered from the Wayback Machine.

Interesting writing and discussion on another perspective about women in technology. This is from the DevChix group, and though I really dislike the use of ‘chix’ and ‘grrl’ when referencing professional women, it’s a good site to discover women working in the newer Web 2.0 technologies.

In the essay, the writer who goes by gloriajw, believes that one of the reasons women have been dropping out of the field is the hostile nature of most tech environments. She addresses this from the perspective of what makes women’s only groups more approachable:

The material for this article came about through my participation in both women-only and mixed gender groups of many kinds. When I wonder why tech groups aren’t tolerable for many women, I look at the inverse of the problem: What makes women-only tech groups more tolerable for women?

Of the behavioral patterns she’s identified in said groups, she mentions a strong sense of community, and in particular how communication is managed:

Destructive criticism is the best way to keep a site predominantly male. It implies that there is no concern about whether a person can learn from a response or not, or whether they would find offense. It is an outward display of ego, a territorial “pissing rite” in which most women do not and will not participate.

In such groups, the author states, bad behavior is seldom called and typically ignored. Contrastingly, in women’s groups:

If you do something awful to one woman in a women-only community, all will hear and know about it, and you are ousted. Most of the time this is first discussed and voted on by many group members. Many times the women’s group will even make an effort to explain the offense to the oblivious offender. But if the offender is still oblivious and/or offending, the offender is out. This is done to protect the interests and goals of the group. Many male dominated online groups don’t run this way. Most if not all women’s groups run this way, whether online or off.

There is a reason why I won’t join such women’s group, and this paragraph more or less sums it up for me. This ‘group think’ way of dealing with difficulty I find, frankly, repugnant. I happen to agree that ignoring a person who exhibits ‘bad’ behavior is one of the better approaches to take. I’ve seldom seem a troll continue when no responds to what they say.

And what is ‘bad’ behavior? When does such voting take place? In the last week I’ve been called both mean and vicious because of my criticism of a company and a company’s actions. Is it then that one must preface all criticism with something sweet and fluffy in order to ease the difficulty of the words? I can’t think of any better approach to shut down all discussion than to have to struggle through some inner debate about how to coach criticism in ‘nice’ terms in order to express such. Weblogging has demonstrated that nice is relative–having to do with popularity, as much as tone and word usage.

gloriasw, has four suggestions for online discussion areas to make them more inviting for women:

  1. Immediately delete offending and off-topic comments
  2. Return aggressive or overly hard comments back to the creator and have them re-phrase
  3. Treat the space like a community, which I presume means to monitor
  4. Explicitly state the site is ‘woman friendly’

She also has approaches to take for men to communicate with women:

  • Don’t assume when a woman is enthusiastic about their work, they’re hitting on you or has to do with you
  • Leave your libido at the door
  • Women aren’t dressing the way they do because they’re sending you signals
  • Something about guy humor can be OK if the first three items are kept in mind

There is some of this I agree with, but I have to ask the question: do women spend all day running from the men in their groups? I’ve rarely had issues of being hit on, even when I was younger and considered ‘purty’. I’ve rarely seen this happen with other women. Is this happening, now, among the younger men? Younger tech guys, do you spend all your time hitting on the women at work?

Too much emphasis lately on women being perceived as sexual object or victim’, and way too much emphasis on how the problems women are having in technology are because men see us as sex objects. I’m sorry, this is not my perception. I’ve been in the industry 25 years, and I’ve rarely seem women hit on at work, nor do I see such behavior in most of the discussions I get involved in.

Does it exist? I imagine so, but I seriously doubt this is the reason women are not joining and are leaving the tech field. Why? Because such behavior is everywhere–it’s not unique to Web 2.0 environments. The feel of titanium or the glow of an LCD does not trigger men into being primal savages.

As for the aggressive nature of the discussions, again, considering that I’m also seen as a ‘aggressive’ communicator, I don’t know if communication style is the problem as much as lack of respect and the communication only reflects this. To me, the larger issue is that women in tech are not as respected as the men, and hence our work is more easily discredited or ignored, our contributions downplayed, our participation compromised. Worse, when we do get into passionate discussion, our arguments tend to be discredited using the too typical ‘shrill’ or my personal favorite, ‘hysterical’.

What concerns me about writings such as gloriasw’s is that this can actually make things worse, rather than better.

The first writing I ever did on sexism in this weblog was related to Doc Searls –yes beloved, gentle Doc Searls. Doc Searls is a nice man, and yes, he does reference and link to women–more than a lot of other guys. But he’ll never get into a discussion with a woman. He will never debate a woman. In close to seven years of off and on reading of his site, I’ve never seen him actually have a truly engaged discussion with a woman. To this day, I don’t know if it’s because he doesn’t respect us, professionally. Or if it’s because he doesn’t know how to have such a discussion without coming across as bully or being abusive. By not engaging with women, though, he does us more harm than if he wrote that we’re all skanky bitches.

If we keep emphasizing about how women need ‘safe’ places, we’re going to get exactly what we’re asking for: safe, isolated, segregated spaces where we never have to worry about harsh words. We’ll also never have to worry about reaching the top positions in our fields, becoming as well known, being invited to conferences, and so on, either.

Respect is the key, not tone of voice, or words used. If a person respects you, it comes across in how they respond to what you say. They may get angry, and they tell you you’re dead wrong, and they may even say you’re being an idiot in this situation. However, if the overall interaction is one of respect, it doesn’t matter the tone in any particular discussion. That’s the real problem we women have: we don’t have the respect that, frankly, we deserve.

Case in point is the Devchix site, itself. This site has been around almost a year, and covers all sorts of topics, including those of interest to the Ajaxian set. Yet, I don’t think I’ve seen any of this site’s writings linked by sites such as Ajaxian. In fact, the same looks to be true for each individual contributor’s weblog–I can’t see that any of these women have been linked by some of the more dominate or well known tech weblogs.

I first found out about this writing at Simon Willison‘s weblog. Yet this is the first time (that I can find through the search engines) that Simon has ever referenced a writing from the site. Or, from what I can see, the individual weblogs of the authors. Yet they write on many topics related to the tech that Simon is interested in.

Simon does point to the Reddit thread, as demonstration that this confirms the writing, but really doesn’t this just confirm that discussions at Reddit (and Digg) tend to degenerate into three year olds flinging shit no matter what the topic? Frankly, as much as I’d like to blame Reddit or Digg or even Slashdot for women leaving tech, I find it unlikely.

Men and women are both equally capable of being aggressive and mean, and though society has educated each sex to express such in differing ways, we need to stop pointing how women are fragile flowers who can’t handle strong disagreement, while all men do is go toe to toe and spit at each other. What we need to question is when there are women in the field, writing on the topics, speaking of such, going to the conferences, why aren’t we given the acknowledgment? Why aren’t we given either the respect due us as professional or the attention we deserve as active participants. At a minimum, why, in this supposedly equal world where no one knows you’re a man, woman, or dog, why aren’t we given the links?

For all that I disagree with gloriasw, I appreciate her post. At a minimum, it highlights yet more women who are working with the Web 2.0 technologies and such attention is a good thing. I just wish when members of the site write on technology, they would be equally as noticed.