There’s no denying it: the economy has gotten shitty. While we over at Object Adjective seem to be going strong, landing contracts and continuing business as usual, you can hardly surf the news feeds on the web without reading one article or another about how unemployment rates have risen to claim over 232,000 jobs since the new year, making this the largest recession since 2003. Unemployment rates at the time of this post are a whopping 5.1% and continuing to climb. It’s a bit scary for all of us here in the US of A, even with the prospect of getting that stupid tool out of the White House.

But the reason I am writing this is not so much to gripe about economics in general as it is to promote a good friend of mine who has lost her design job to the current recession.

Her name is Vara Pappas and she is a hell of a print designer and a damn good fashion photographer as well. This past Monday she received notice that she was being downsized by her company due to a lack of incoming work. They ensured her that she would be awarded 2 weeks of severance pay, but this is hardly a treat when you live in San Francisco, one of the most expensive cities in the US. She needs to find a job that will give her the opportunity to do what she does exceptionally well, and fast.

So, if you’re hiring a print designer, or you know someone who is, check out her website.

Note: She’s also willing to take freelance projects for the time being as well until she finds something more permanent, so don’t miss out on the opportunity to work with her.

A few weeks back, along with many others in the development community, I wrote in response to Microsoft’s announcement that IE8 would implement version targeting, a means of back-dating a site so that it doesn’t break with new releases of the browser.

While my views expressed in Version Targeting: Defaulting to the Past to Spite the Future? were primarily favorable of the new technique, I expressed my concerns with Microsoft’s decision that IE8 and all other browsers to come would default to rendering as if it were the previous release of the browser if the meta tag, which looks like this:

<meta http-equiv=”X-UA-Compatible” content=”IE=x;FF=x;OtherUA=x” />

was omitted, rather than in the current up to date standards mode. Perhaps the pressure of the masses in the standards community, Microsoft has caved and agreed that the default rendering engine of IE8 will now favor standards compliance rather than giving precedence to the fear of breakage. To quote their March 3rd press release:

Microsoft Corp. is now configuring the settings in Internet Explorer 8, the upcoming version of its browser, to render content — by default — using methods that give top priority to Web standards interoperability.

While their official position is that they have reoriented their company focus away from proprietary winner-take-all competitiveness and toward interoperability, a lot of us (those not so trusting), posit that they most likely just couldn’t stand up to the pressure coming from those aligned with the web standards movement.

Honestly, it doesn’t really matter what contributed most to their decision. Either way you look at it, progressive support for standards is a good thing. In the end, with IE8 now in public beta, it seems the IE team is finally looking forward like the rest of us, instead of shoving their proverbial heads up their own asses. Standards will be supported by default.

This week has brought an exciting new development in my life: I got accepted to the Studio Residency Program at Root Division, a nonprofit arts organization here in San Francisco’s Mission District. A few weeks ago, due to the urgings of friend and artist Deric Carner, I made the decision to apply to the program.

After speaking to the director on the phone about the application process, I quickly slapped together my portfolio, resume and finished updating my art portfolio website. That same afternoon I crossed my fingers and dropped off a folder containing evidence of my fine arts career to date. Anyway, to make a short story shorter, I interviewed and received notification 2 days ago that I got in. So I am officially going to have a studio space! I can barely contain myself, I’m so elated.

The program over at Root Division is great - you get a studio space at a much lower than market rent, and in exchange you just have to spend a few hours a month doing some sort of service for the organization. You can help with any number of things ranging from teaching community art classes to hanging exhibitions in their gallery space. In my case, they might also have me help out a bit with their website, since, as you know, this is my “thing.” I definitely consider the opportunity to be involved with the organization and spend some of my free time helping them out to be a perk rather than a burden.

As a studio resident, you also get the opportunity to show your work in their gallery, curate art exhibitions, and just be around the other studio artists in the program. Having gotten out of graduate school over 2 years ago, it’ll be great to interact with other working artists again on a day to day basis and be a part of the dialog.

So in addition to working full time on web design and development and running our company, I will be painting again and making other forms of art. It’s been a while since I’ve had a space to carry out my more involved art projects. I can’t wait to get started.

The past week has been a whirlwind of events, with art as the focus. For the last year since starting our design business Object Adjective, I’ve been more or less out of the art scene - always dabbling on the periphery but not as involved as I once was. And while I love working in web design and development, it used to be that the practice of artmaking informed my design, my code, and vice versa. Continuing to work as an artist and stay engaged in the art and music scenes is important to me, and this past few days has served as a reminder.

A Little Bit Edwardian

Last Friday night was the Edwardian Ball - this year themed World’s Faire. Set at the Great American Music Hall, the gold leafed ornate detail of the old theater was the perfect backdrop for a night riddled with corsetry fashion shows, Edward Gorey inspired poetics and visuals, diverse Edwardian inspired music, art exhibits, and acrobatic performances.

Jeremy, Mici, August and I decked out in our turn of the century best, snapped a few pics at my apartment, and headed out to enjoy a night of music, art, and performance. The event was spectacular - with so much to see and do. Read the rest of this entry »

The topic of version targeting has been all the rage the last 2 days, following Aaron Gustafson’s article for A List Apart and Eric Meyer’s companion piece. IE8 has not only passed the Acid2 test, but in this release it will be taking a new direction on version control, allowing us developers to, rather than rely on the DOCTYPE declaration to attempt to keep our sites in rendered intact, asign a meta element with the browser versions for which the site was coded and tested against. This meta element would look like this:

<meta http-equiv=”X-UA-Compatible” content=”IE=8″ />

Of course, in theory, if all browsers adopt version targeting, you would be able to enter content=”IE=8, ff=2.1, saf=3.0;” so all browsers would perform as though it was the day you coded it.

The logic Microsoft uses to explain their reasoning for going this route in IE8’s development makes perfect sense:

We realized that “Don’t Break the Web” should really be translated to “Don’t change what developers expect IE to do for current pages that are already deployed.”

The benefit, of course, is that if you code and test in IE6, you state this in the meta element or HTTP header, and the browser “pretends” to be IE6 and renders the site accordingly, behaving as the back version of the rendering engine would have. Great. So your code is locked in time, and no matter how many versions of a browser come after, your site will not break. It’ll look the same forever.

However, if you omit the meta http-equivalent, the browser just acts as the backdated version - so IE 8 will act like 7 and render the page using the IE7 rendering engine instead of defaulting to the current standards mode. Read the rest of this entry »