|«« Using Third Party Libraries for a Software Project||Testing is a First Class Job »»|
I'm Ryan Lowe, a Software Engineering graduate living in Ottawa, Canada. I like agile software development and Ruby on Rails.
I write this blog in Canadian English and don't use a spell checker. Typos happen.
» Full-time Ruby on Rails freelancer
» Full-time with Rails since May 2005
» Former committer for RadRails (now Aptana)
» I also have a few Rails side-projects in development:
1. wheretogoinTO.com Toronto nightlife
2. Hey Heads Up! TODO list and sharing
3. Layered Genealogy family history research
4. foos for foosball scoring
5. fanconcert for music fans (on hold)
Hiring Rails developers? I can telecommute by the hour from Ottawa, Canada
»» Email: rails AT ryanlowe DOT ca
Now hosted on Hey! Heads Up -- check it out!
Derek Lowe's (Ryan's older brother) words at Ryan's funeral
email@example.com no more
Forging Email Headers: Good, Bad or Ugly?
Sarcastic Dictionary (Part 1 of Many)
Twisting Rails is Risky Business
Risky Business? My Take on Early Alphas
Whoa, it's August 2007
A Postscript to "Growth at the grassroots"
»» All Blog Posts
David Heinemeier Hansson
James Duncan Davidson
Signal vs. Noise
Amy Hoy: (24)slash7
Luis de la Rosa
Ahhh the Memories
I'm getting a few hits from Dave Winer about this problem again. He likes to link to posts from the same day in years past. It was my first link from a mainstream blogger and it pretty much got me hooked on link trolling. ;) hehe
So what's happened with this problem? People are still running into it (with old versions of MT presumably) -- I can tell by my hit counter. Just goes to show you: don't underestimate the reach your software can have, it'll bite you. This was a particularly silly booboo too given it affected Internet Explorer, a browser with over 90% market share at the time.
What was the root of the problem? A broken implementation of a standard: a bad library plus poor checking by the developer equals unhappy end users. It wasn't the CSS coder's fault that IE broke the spec, but it was his fault that he didn't verify it. Read my previous post today for more of my thoughts on issues with third-party libraries.
Oh and by the way, let's not forget that there was another IE-specific problem with that CSS stylesheet too. MovableType is a great product but those kinds of errors in a default stylesheet were just not cool. Lesson learned.Posted at April 26, 2004 at 07:59 AM EST
Last updated April 26, 2004 at 07:59 AM EST