Posts in the Tech Category

Valid Concerns

Published 21 years, 7 months past

I hate (American) sitcoms and soap operas.  That’s a sweeping generalization, a trend that seems to be sweeping the Web of late.  No choice but to continue.

The majority of American sitcoms derive their humor—or, from my perspective, “humor”—from characters getting into embarrassing situations and then trying frantically to get out of them.  The laughs are generated by watching this person be humilated, often at length.  Generally, the humiliatee is receiving some form of just desserts: they got themselves into the situation through selfishness or arrogance or some other form of hubris, and end up paying the price.  In any event, they get to squirm and flail before our eyes and it’s funny!  Only it isn’t.

I dislike American soap operas not because they’re harshly lit and seem like community theater writ large.  I have no issues with the acting, which is actually fairly impressive in terms of the quality-to-quantity ratio.  I dislike soap operas because they’re nothing but sturm und drang, one melodramatic setpiece after another.  The number one rule is, nobody gets to be happy for long.  Anyone who does find happiness is just being set up for a major, major trauma, likely at the hands of whoever is currently making them happy.  (Although death is far less traumatic in soap operas than in real life, as people come back from the dead and aren’t even zombified when they do.  Which I suppose is good news for the power grid.)  There’s only so much of the constant chest-heaving, garment-rending dramatics I can handle before I glaze over and start to closely contemplate my cuticles.

Now why would I be talking about this when everyone else is talking about validation?  It’s a mystery, I agree.


Code Constraints

Published 21 years, 7 months past

Chris Adamson has an interesting post over at the O’Reilly Network about code in books and articles.  In summation: should code be given a special license, separate from the actual text?

While CSS isn’t code, exactly, the same basic questions apply to the stuff I’ve written.  Let’s take my most recent title, More Eric Meyer on CSS.  It contains a copyright statement that says, in effect, you can’t reproduce the book’s text, in part or in whole, without permission.  There is no distinction there between the explanatory text (“Margin collapsing is an interesting problem in some cases, and here’s why, blah blah blah…”) and the styles.  Taken literally, the copyright statement says that you can’t re-use any of the CSS I created in your own designs.

This is clearly in opposition to what I think most of us would agree is the expectation, which is that you can use styles (or code) as you see fit but you can’t take the ‘narrative’ text and pass it off as your work.  But where’s the dividing line?  Suppose that, for whatever reason, you really like one of the designs in Project 4.  We can agree that you should be able to re-use the styles presented, but a whole design?  Is that fair?  I can imagine many arguments both for and against, many of them variants on the classic slippery-slope argument.

In my particular case, the situation is even less clear.  As anyone who drops by the book’s site will discover, the project files are freely available for anyone to download.  You aren’t even expected to own the book as a condition of using them.  That makes them less protected, I would think, than if they were on a CD that accompanied the book—but how much sense does that make?  Again, I can envision several arguments on both sides of the issue.  The same questions would arise for any author that provided code samples for download, as many do.

There’s also the question of what rights can or should be granted to the reader with regard to code.  I might hypothetically make the styles all freely available to anyone, but only under the condition that attribution be given to the source (either me, the book, or both).  Wouldn’t you, as a reader, find that rather annoying?  I would.  “You mean I have to give Eric credit just to use two CSS rules that create this cool effect?”

I’ve always operated on the principle that any markup or CSS I write about is fair game, because otherwise what would be the point of writing about how to use it?  I can see it now: “use of the CSS presented in this tutorial, including any derivative works, without the written consent of the author is prohibited.”  Yeah, right!  That would be something like a dictionary prohibiting you from using any words you look up, including all modifications and misspellings.

So should books contain an explicit license regarding use of the code?  If so, what kind?  I expect readers and publishers will have different viewpoints, although the more clueful publishers probably won’t be too far away from the typical reader perspective.  There’s a part of me that wonders why we even have to be explicit about this at all—after all, there’s been a sort of tacit acceptance of code re-use to date—but in a litigious DMCA world, this is an issue that probably has to be addressed sooner or later.

As I ponder the subject, I’m currently contemplating putting all my code samples under a Creative Commons ShareAlike 1.0 license, both now and into the future, just to make sure the bases are covered.  Then again, perhaps an explicit Public Domain license would make more sense.  Which one would be better, or is there a superior approach I haven’t considered?  Let me know.


Edged Out Of Contention

Published 21 years, 7 months past

Andrei fired off round two of “Gurus vs. Bloggers”, and good news!  I played on the guru team by proxy, and was defeated by Dave Shea‘s proxy, more or less as I’d hoped I’d have the chance to do after round one was played.  Andrei was nice enough to hem and haw about which one ought to win, but honestly, there wasn’t much contest.  The Zen Garden won two SXSW Web awards including Best In Show, after all, not to mention the awe and respect of Web design folks the world over.  css/edge, at best, earned awe and respect.  In any case, I am honored to have been so thoroughly owned by the man Andrei calls “one of [my] best students.”  Mr. Shea, I bow to you.

In his tongue-in-cheek commentary, Andrei said:

Maybe if Meyer had used orange for CSS Edge, because orange is after all the new black, I would be able to swing the vote the other way.

I don’t know—low-contrast orange doesn’t really seem much better than low-contrast blue, does it?


Self-Referential

Published 21 years, 7 months past

A week ago, I published an entry that was two parts exploration and one part experimentation.  The experiment was to see how readers commented on a post of that nature, one that was potentially very inflammatory even though was not at all its intent.  The commenting ability is still new for me, and I’m working out how open I want to be about comments.  When I was writing the entry, I had in mind to not permit comments, realizing that it could easily draw a metric ton of flames, accusations, and other sundry ickiness.  At the last minute, I decided that it would be better to open comments and see what happened.  I’m well satisfied with the results, but have now closed comments on the entry (you can still ping it if you want).

I do want to follow up just a bit on some of the comments that were posted.  A few people said or implied that I should have picked a less volatile subject than intimate partner violence (IPV).  That’s just it, though: I didn’t pick the subject with an intent to post.  I was doing my own research, for my own information, and at the end of the process decided I’d share the results rather than just sit on what I’d learned.  Why?  I’ll quote myself:

…I was able to do some in-depth fact checking of my own in less than an hour, using nothing but Google and some well-chosen search terms, and obtain a more accurate picture of the world than I’d had before. I believe that this ability to self-inform is one of the most important and often underappreciated benefits of the Web. If nothing else, I’m glad I went on this particular search because it reminded me that the Web really is something worth fighting for, and that improving the Web is always an effort worth undertaking.

It was an aspect of the Web I’d rediscovered, and thought it was also important to share.  I’ve been doing this stuff for more than a decade now, and when I started my whole goal was to help put information online.  That’s why I wrote the HTML tutorials at CWRU—to make it easier for people to share information about whatever they knew best.  I’ve seen a resurgence of that impulse recently, with people blogging obscure fixes or problems they’ve encountered so Google will pick it up, and it will be there for the next person who needs it.  (See, for example,”Writing For Google” over at Daring Fireball.)  So if I can forget that the Web is an astonishing source of information, and need a reminder, maybe others could use the same reminder.

And why did I share so much detailed information on such a potentially sensitive subject?  I don’t think my points would have had the impact without the details.  That probably sounds like I was trying to use a touchy subject to raise my exposure, but that’s not it at all.  If I’d just posted to say, “I was curious about something and dug up a lot of information about it, and that’s what’s cool about the Web” it wouldn’t have had the same resonance.  Walking through the process and pointing to the sources I quoted established a context for my final points.  It was also the case that I believe I found some useful information about a very important subject, and was able to disseminate it further.

My thanks to everyone who contributed comments, especially those of you who pushed back a bit.  I’ll close with a favorite David Byrne lyric; make of it what you will.

Facts are simple and facts are straight
Facts are lazy and facts are late
Facts all come with points of view
Facts don’t do what I want them to
—”Crosseyed and Painless”

My Dinner With Brian

Published 21 years, 7 months past

I was back in the training groove this week, and on Monday morning one of the attendees had to duck out at one of the breaks.  “I have to talk with Brian, who’s consulting for us.”  I must’ve looked blank, because he said, “Brian Foy.  Do you know him?  Works with Randall Schwartz.”

I’ve been reading Brian‘s missives from Iraq on the O’Reilly Network for a year now, and was really psyched to meet him.  As it turned out, we both were planless on Monday night, so I picked him up at his hotel and blundered around the neighborhood until we found a Thai restuarant.  Over appetizers, Brian told me his wife (an opera singer) has been doing her own Web design for a while now, and was getting into CSS.  Then he mentioned buying the O’Reilly CSS book for her, and as he talked about why he’d bought it, I quickly realized that he’d picked it up because it was an O’Reilly book, and recommended.  He literally didn’t know he was having dinner with its author.

After a couple of minutes, I finally told him who’d written the book.  I should probably feel bad about not admitting it right away.  I wasn’t going to say anything here either, but he already blogged it, so… what the heck.

It was very interesting to talk about Iraq with someone who’d been there.  I was able to ask him the question I’ve wanted to have answered for a while: “How does the news coverage compare to what’s really going on over there?”

“It’s horrible,” he said.  “We got CNN and Fox on the Armed Forces Network and they were both just terrible.”  He said that he’d literally been present for things that were being covered on TV by the time he got back to the barracks, and nobody ever accurately represented what had happened.  Not even close, apparently.  Brian made the observation that images are so overwhelming, so powerful, that the story was always driven by whatever footage had been shot.  Not by the actual event in its totality, nor the context.  Just the visual.

It wasn’t surprising to hear that, but it left me saddened and frustrated.


Earning A Spot

Published 21 years, 8 months past

Through a winding chain of links—it was, of all things, the result of an extended surf on the Web, and who does that any more?—I came across Cameron Moll‘s “80/20 and the design blogosphere“, where he listed the 20 people from whom he feels 80% of vital new media design information flows.  I was deeply flattered to be on the list, although I again feel weird about it.  I don’t give out design information, and meyerweb is certainly nowhere near as well-designed as many sites (including Cameron’s).  Heck, I don’t even talk about CSS all that much any more, despite numerous vows (public and personal) to do otherwise.  I suppose all the books and other writings allow me to coast into these lists, and that’s a nice feeling, but I’m starting to seriously ask myself what I’ve done for everyone else lately.

So I’ll throw it open to the crowd: what kind of information, new media design or otherwise, would you like to see from me?  What do you feel would earn me the right to stay in Cameron’s 80/20 list?  Post and ping, or contribute a comment.  Your choice!

(I have to shoot down one potential request now: I’m not going back to browser support charting.  Westciv does a decent job already, and as I wrote a while back on www-style, going any further is a massive undertaking.  And, to be honest, it’s mind-shatteringly dull and incredibly time-consuming.)


We Need Some References, STATS!

Published 21 years, 8 months past

During a recent (somewhat contentious) debate, a friend tossed out the statistic that every nine seconds, a woman is beaten in the United States.  Later on, I did some math, and determined even if we assume that every one of those beatings is suffered by a different woman—that is, no woman is beaten more than once in a given year, which is most certainly not the case, but we’ll take it as a premise anyway—that means just over 3.5 million women are beaten every year.  That’s fairly shocking, if it’s true, since that’s about 2.5% of all females in the country (of all ages; there were approximately 144 million females in the U.S. as of March 2002, according to the Census Bureau document Women and Men in the United States: March 2002).

But is it true; or more appropriately, is it an accurate reflection of what’s really happening?  I started to wonder about this, because I have a tendency to question premises pretty closely.  What’s meant by “beaten”—does it include incidents where a single punch is thrown in anger, and instantly regretted?  Does it refer only to reported incidents, or is it based on both reported and estimates of unreported incidents?  Does medical attention have to be sought?  Does it include beatings of women by women, or is it only concerned with times when a man beats a woman?

So I turned to Google to do a little basic research.  The search “woman beaten every seconds” immediately turned up claims that varied from every nine seconds to every fifteen seconds.  That latter interval would mean that about 2.1 million women are beaten every year, again assuming every incident involves a newly beaten woman, which is quite a drop from 3.5 million.  I also found STATS.org, a site that claims to “check out the facts and figures behind the news.”  They claim, in a list of what they term “commonly accepted fallacious statistics,” that the actual interval is every two minutes twenty seconds, based on a figure of “220,000 serious violent incidents” for calendar year 1999.  Which works out to every two minutes 23.34 seconds—if it’s true.

But is it?  Our friends at STATS aren’t much help, because they provide no direct reference for the figure, so there’s no easy way to check up on their methodology either.  Further obscuring the picture is that they don’t define a “serious violent incident.”  To reiterate some earlier questions, does it refer only to reported incidents, or is it based on both reported and estimates of unreported incidents?  Does medical attention have to be sought in order to count as a “serious” incident?  They aren’t saying, nor do they provide any links to more detailed information.

So I started digging a little more deeply, again through Google.  Eventually I found a document on “Intimate Partner Violence” (and more on that in a moment) at the Department of Justice that reports:

  • The number of female victims of intimate violence declined from 1993 to 1998.  In 1998 women experienced about 900,000 violent offenses at the hands of an intimate, down from 1.1 million in 1993.
  • In both 1993 and 1998, men were victims of about 160,000 violent crimes by an intimate partner.
  • Considered by age category, 1993-98, women ages 16 to 24 experienced the highest per capita rates of intimate violence (19.6 per 1,000 women).
  • About half the intimate partner violence against women, 1993-98, was reported to the police; black women were more likely than other women to report such violence.
  • About 4 of 10 female victims of intimate partner violence lived in households with children under age 12.  Population estimates suggest that 27% of U.S. households were home to children under 12.
  • Half of female victims of intimate partner violence reported a physical injury.  About 4 in 10 of these victims sought professional medical treatment.

So that gives us some actual numbers into which we can sink our calculators.  I’ll take one million as an average for the period 1993-1998, which is a crude but convenient measure.  That works out to a beating every 31.536 seconds; we’ll round down to every 31 seconds.

There are three things to note here.  One, this is “intimate partner violence,” which includes spouses, ex-spouses, boy/girlfriends, and ex-boy/-girlfriends.  It therefore doesn’t count random attacks like violent muggings, rapes by strangers, and so on.  Two, there were a million violent offenses, which does not necessarily mean a million different women, but there’s no way to measure that so we’ll continue to assume that every incident involves a different woman.  Three, it’s stated that about half of such violent incidents are actually reported to the police, which means there’s potential uncertainty in the data set.  The description of methodology restores some confidence; in the period 1993-1998, they interviewed “approximately 293,400 households.”  That’s a pretty good data set.

The report also states:

Women were more likely to be victimized by a nonstranger, which includes a friend, family member, or intimate partner, while men were more likely to be victimized by a stranger.

“More likely” doesn’t give us much of a handle on the proportion of intimate-to-stranger violence, unfortunately.  If intimate partner violence constitutes 55% of all violent crimes against women, that’s a much different story than if it’s 90%.  Furthermore:

Sixty-five percent of all intimate partner violence against women and 68% of intimate partner violence against men involved a simple assault, the least serious form of violence studied.

“Least serious” is a bit of a misnomer, in my opinion, since “simple assault” is later defined as:

Simple assault is an attack without a weapon resulting either in no injury, minor injury (such as bruises, black eyes, cuts, scratches, or swelling) or an undetermined injury requiring less than 2 days of hospitalization.  Simple assaults also include attempted assaults without a weapon. 

So a slap in the face is lumped in with a beating that leaves marks or requires up to two days in the hospital.  We’re also including incidents where a person (male or female) tried to attack a woman without making use of a weapon, but failed.  Or succeeded.  That’s a very, very wide range of incidents and types of violence.

Since the next step up in assault severity is aggravated assault, which includes incidents in which “the victim is seriously injured,” we could decide to count all non-simple assaults as serious violent incidents.  That would mean around 350,000 such incidents in a year, which is obviously higher than STATS’ figure of 220,000 for 1999.  Now, I suppose it’s possible that the figure dropped that much between 1998 and 1999, but I give such an occurence a probability somewhere around that of my being made the first astronaut to Mars.  So we’re still left wondering what “actual figure as estimated by the Justice Department” they’re using, since the actual figures I got from the Justice Department seem to have nothing to do with their figures.  (But at least I pointed you to my source, so you can check up on my assertions; see the Bureau of Justice Statistics’ main page on Intimate Partner Violence to get links to PDFs, Excel spreadsheets, the document I’ve been referencing, and more.)

At the end of all this, we seem to have arrived at an answer between the commonly-repeated figure of “every nine seconds” and STATS’ claim of every two-and-a-third minutes (which in turn leads me to harbor deep skepticism about their other claims, since their domestic violence number seems to be, well, fallacious).  As noted, the numbers I’ve been using all cover intimate partner violence.  I didn’t find similar information on other kinds of violence, although I’m sure it exists somewhere.  Once those incidents were added in, they would lower the average interval between beatings, although they couldn’t lower the interval all the way to nine seconds, or even fifteen.  To do that, there would have to be more stranger-perpetrated violence than intimate partner violence, which the report says isn’t the case.

So what’s my point?  I have three, as it happens.

My first point is that obtaining an accurate picture of the world is a messy, complicated business, and simple unattributed figures don’t help at all.  I’m not trying to say that violence against women isn’t a big deal: it is.  I personally think violence of any kind, no matter who is the victim and whom the attacker, is a big deal, and we should work to lessen such incidents.  I am saying that it may or may not be as bad as we think—and, in fact, the document I used states that intimate partner violence and homicides dropped over the covered period, despite the fact the national population was rising.  That says to me that we should work harder to figure out the causes driving that decrease, and exert more efforts along the same lines.  I’m not so naïve as to think we can ever totally eliminate violence, but we can and should do our best to get as close to that goal as we can.

My second point is that the news media don’t help at all in clarifying this stuff—no great shock there, I suppose, but it’s something that been bothering me more and more of late (as I wrote yesterday).  I previously linked to an article about the gross inaccuracies in reporting about the cost of the proposed missions to the Moon and Mars, and this is another example of how convenient, unexamined “facts” become common conversational currency.  I know I’ve heard the “every nine seconds” figure on the news, or at least a figure very much like it.

The third and perhaps most important point, and the one I found most personally fascinating, is that I was able to do some in-depth fact checking of my own in less than an hour, using nothing but Google and some well-chosen search terms, and obtain a more accurate picture of the world than I’d had before.  I believe that this ability to self-inform is one of the most important and often underappreciated benefits of the Web.  If nothing else, I’m glad I went on this particular search because it reminded me that the Web really is something worth fighting for, and that improving the Web is always an effort worth undertaking.


Migration Patterns

Published 21 years, 8 months past

I’ve fielded a few questions about my experience migrating from Movable Type to WordPress, so I thought I’d address that subject for anyone else who might be interested.  I didn’t migrate from Movable Type.  I’ve never run Movable Type.  Okay?  That’s not saying anything for or against MT.  I’ve just never used it.

What I was using before setting up WordPress was a completely hand-built system where I authored entries in an XML format of my own devising, in which every entry for a given period (say, all of 2004) was sitting the same file.  Once I wrote a new entry, I’d pour the XML file through a set of XSLT scripts to generate the latest posts, monthly archive pages, and RSS feeds.  This was accomplished with some dirt-simple shell scripts I’d put together.  Here’s what the main script looked like:

#!/bin/bash
MONTH="$(date +%Y%m)"
echo $MONTH
xsltproc -o latest.html xslt/latest.xsl archive.xml
xsltproc -o rss20.xml xslt/rss20.xsl archive.xml
xsltproc -o rss091.xml xslt/rss091.xsl archive.xml
xsltproc -o $MONTH.html -stringparam chunk $MONTH xslt/chunker.xsl archive.xml

Anyone familiar with xsltproc will see what I’m doing at a glance.  For the rest of you, here’s a quick explanation.  The first xsltproc... line runs xsltproc using the script at xslt/latest.xsl (relative to the shell script) against the file archive.xml, writing the result to the file latest.html.  That’s it.  Nothing very fancy, but it worked well enough when I created the system.

Why did I abandon my loving crafed system for an installable package?  A combination of factors, any of which would not have been enough on its own.

  • The monthly archives were starting to get too heavy.  For example, the archive page for March 2004 is 88KB, and that doesn’t count any style sheets, images, or other external resources that would have to be loaded on top of that.  Back in the day, a month’s worth of posts would be maybe 15KB of HTML and text.  Heck, all of my posts from 1999 and 2000 total a whopping 32KB of HTML source.  My total posting from December 1999 through 2001 is about the same amount of data as the posts for March 2004.  So I needed more flexibility in terms of post archiving, which meant things like per-post archives, which I didn’t really want to have to try to support via XSLT.
  • I wanted to offer post commenting from time to time, and also have a system that managed pingbacks and trackbacks.  I had very little interest in figuring out how to implement my own commenting system, so weblogging software was my best choice.
  • An ability to search through the post archives was something I wanted to add, but for some reason I don’t want to do it through Google.  I’m still not sure why… I just don’t.

So why did I migrate to WordPress, specifically?  After looking at a number of packages, I decided that WordPress just fit me the best.  I still don’t like having to go through a Web interface to write posts, as I’ve gotten very used to authoring in BBEdit, but that was going to be a hurdle no matter what.  (And I do often write up a post in BBEdit before simply pasting it into the Web interface.)  Here are some specific reasons:

  • By default, WordPress generates valid XHTML files.  Thus, the process of adapting its code to generate the valid HTML I wanted was a lot less painful than it would have been with a package that doesn’t generate valid markup by default.
  • Similarly, WordPress is set up to handle site presentation via CSS, so it was a trivial matter for me to replace their default styles with my own.
  • I like that WordPress is not only open source, but users are encouraged to hack on it and share their hacks, which I’ve already started to do.  This was enough like a hand-built system to make me happy.  I think of it as a stock car that I can tune and tinker with to my heart’s content.
  • The new “Import via RSS” feature in WordPress 1.2 made sucking all of my back posts into the system really, really easy.  I just had to create a full-content RSS file containing every post I’d ever written—pretty easy, given that I had them all stored in XML—and then point the RSS importer at the file.  Well, two files, actually, but it still made the whole process very smooth.  It read the publication dates, categories, and everything else of note in a matter of milliseconds.  In fact, it was so easy I felt no regret about blowing away my test-site import and doing it again for the public site.
  • It certainly didn’t hurt that one of the primary forces behind WordPress is Matt Mullenweg, a fellow GMPG founder, so I knew that if I really got stuck I could ask him for help.

So that’s why I switched away from my home-brewed system and onto WordPress.  So far, aside from the occasional bouts of swearing at obscure MySQL and PHP syntax, neither of which has been anywhere near as migrane-inducing as XSLT syntax was, I’ve had no significant reason to regret the change.

Now you know… and knowing is half the battle.


Browse the Archive

Earlier Entries

Later Entries